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
We're trying to serve some Gatsby pages by using Nginx to rewrite the page URLs, but it seems that Gatsby depends on the page URL to reference a direct path on disk--I get the following console errors when I then try to access these sites (we're rewriting URLs such as /hotels-ng?district=1234 to page directory paths such as public/district_1234):
A page wasn't found for "/hotels-ng"
loader.js:259:8
A page wasn't found for "/404.html"
I saw that a similar question about path rewriting was raised in #383 but that issue is over a year old and the advice there seems to be outdated, so I figured that I'd raise it again. Like, is this the new example that I should be following? Looking for any guidance really. Thanks!
The text was updated successfully, but these errors were encountered:
We're trying to serve some Gatsby pages by using Nginx to rewrite the page URLs, but it seems that Gatsby depends on the page URL to reference a direct path on disk--I get the following console errors when I then try to access these sites (we're rewriting URLs such as
/hotels-ng?district=1234
to page directory paths such aspublic/district_1234
):I saw that a similar question about path rewriting was raised in #383 but that issue is over a year old and the advice there seems to be outdated, so I figured that I'd raise it again. Like, is this the new example that I should be following? Looking for any guidance really. Thanks!
The text was updated successfully, but these errors were encountered: