Hi Titus,
No way to circumvent the issue. the “#” in URL’s means “the browser handles this” - so our server never even sees the rest of that path - we get:
for a URL like https://yoursite.com/#anything-here-is-never-sent
You’d potentially be able to do a client side redirect - I think the browser is aware that the URL contains it and so you could parse it from there and send a 301 from the client side JS.