-
Notifications
You must be signed in to change notification settings - Fork 86
[Bug]: 404s with dynamic routes and reverse-proxy using basePath #965
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
Comments
Customer updated to release version (December 14 2021) and still seeing issue. |
Minimal repo and steps to reproduce: Repository: https://github.com/RaulEscobarRivas/gatsby-proxy Steps to reproduce:
Expected Result Dynamic path page is served Actual Result 404 Humio query showing request_id |
There is a 404 for this URL: That is being proxied by one of these autogenerated rules:
to here: It should work but it doesn't. However, the direct URL (not proxied) does work, examples below. The first request is the direct request which returns a 200. The second is proxied and is a 404:
|
Steps to reproduce
Go to https://www.tourlane.de/traveller-crossing
Login using the following credentials:
email: [email protected]
password: netlifytest
On the landing page, click either the "South America" or "Europa" continent chip, or any of the links on the pink sidebar (Inspirationen deutsch or Angebote1)
Expected behavior:
Page is served correctly
Actual behavior:
We get a 404 page
Now repeat the exact same steps but instead of using the reverse-proxy from tourlane.de, visit directly the netlify site (https://traveller-crossing.netlify.app/) you will see that this error doesn't happen. Something interesting to note is that after visiting some of the pages on the netlify site, and going back to try to visit them from the reverse-proxy version (https://www.tourlane.de/traveller-crossing) they will work, as it seems that a cached version is being served.
There seems to be some configuration off with dynamic routes and reverse-proxy on Netlify using basePath.
This is working in Vercel.
A link to a reproduction repository
No response
Plugin version
@netlify/[email protected]
More information about your build
netlify.toml
)What OS are you using?
No response
Your
netlify.toml
filenetlify.toml
next.config.js
Relevant log output (or link to your logs)
Build logs
The text was updated successfully, but these errors were encountered: