Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Angular universal with HashLocationStrategy #717

Closed
tami-k opened this issue May 18, 2017 · 2 comments
Closed

Angular universal with HashLocationStrategy #717

tami-k opened this issue May 18, 2017 · 2 comments

Comments

@tami-k
Copy link

tami-k commented May 18, 2017

I am wondering if angular universal actually supports HashLocationStrategy. And if it does, I am curious how the server knows which route is being requested?

@PatrickJS
Copy link
Member

https://tools.ietf.org/html/rfc2396#section-4

When a URI reference is used to perform a retrieval action on the identified resource, the optional fragment identifier, separated from the URI by a crosshatch ("#") character, consists of additional reference information to be interpreted by the user agent after the retrieval action has been successfully completed. As such, it is not part of a URI, but is often used in conjunction with a URI.

The server is unaware of the hash by design. On the server you can generate the correct hash url for links but in terms of rendering a certain page you need another way to tell the server which page to generate

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants