You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is linked to #9714 which fixes this issue for query parameters.
As discussed with @dthyresson , the Redwood dev server returns 404s when there is a . in a path parameter. E.g. the url http://localhost:8910/somepath/1.2/view would 404 even with a matching route. If you navigate to the route on the client, there is no error but reloading will make a request to the server.
This is not the case for production for a) a standard Netlify deployment or b) the recommended Heroku deployment with nginx. Instead, the static file server will always return index.html if there are no assets found to match the uri.
There are a few workarounds for this
Let dev fail when you reload, and test by navigating to the URL you are working on
Replace . with another character when writing and reading the url
Put the . in a query parameter, which means you loose typing (and the URL is very long in my case)
It should be fairly simple and safe (noting the existing production functionality) to fix this by returning index.html instead of a 404.
How do we reproduce the bug?
Make any path with a String parameter in the router, and load a url with a . somewhere in the paramater.
What's your environment? (If it applies)
No response
Are you interested in working on this?
I'm interested in working on this
The text was updated successfully, but these errors were encountered:
What's not working?
This is linked to #9714 which fixes this issue for query parameters.
As discussed with @dthyresson , the Redwood dev server returns
404
s when there is a.
in a path parameter. E.g. the urlhttp://localhost:8910/somepath/1.2/view
would 404 even with a matching route. If you navigate to the route on the client, there is no error but reloading will make a request to the server.This is not the case for production for a) a standard Netlify deployment or b) the recommended Heroku deployment with nginx. Instead, the static file server will always return
index.html
if there are no assets found to match the uri.There are a few workarounds for this
.
with another character when writing and reading the url.
in a query parameter, which means you loose typing (and the URL is very long in my case)It should be fairly simple and safe (noting the existing production functionality) to fix this by returning
index.html
instead of a 404.How do we reproduce the bug?
Make any path with a
String
parameter in the router, and load a url with a.
somewhere in the paramater.What's your environment? (If it applies)
No response
Are you interested in working on this?
The text was updated successfully, but these errors were encountered: