We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As a principal all hash urls should be available as actual urls, presenting the same content.
This can be achieved with the same client code - rewriting the URLs back to the main index.
Currently the main router looks up the URL and expect to find different Routers based on the path (up to one level).
It would be nice if in addition pushstate URLs were supported - possibly by switching between the two processing methods with a flag.
Here's a relevant discussion:
http://stackoverflow.com/questions/9184959/rewriting-nginx-for-pushstate-urls
The text was updated successfully, but these errors were encountered:
#16 adding a few flags to monitor the env (+pushState)
013156c
No branches or pull requests
As a principal all hash urls should be available as actual urls, presenting the same content.
This can be achieved with the same client code - rewriting the URLs back to the main index.
Currently the main router looks up the URL and expect to find different Routers based on the path (up to one level).
It would be nice if in addition pushstate URLs were supported - possibly by switching between the two processing methods with a flag.
Here's a relevant discussion:
http://stackoverflow.com/questions/9184959/rewriting-nginx-for-pushstate-urls
The text was updated successfully, but these errors were encountered: