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 was to fix that the fact that HTTP was not correctly being redirected to HTTPS by Netlify on first load on a fresh cache.
When building with new @next.55, my _redirect file is being copied over, but it is not including the necessary * /.netlify/functions/render 200, which seems to be needed to render the entire app. It seems to work correctly if you have no pre-existing _redirect file.
Reproduction
Add _redirect file to Static folder, and cry as your app is put into the magicians hat.
Describe the bug
Bug was introduced in recent Edge Function updates (even when not using the feature).
I had a _redirect file that had one line,
http://example.com/* https://example.com/:splat 301!
This was to fix that the fact that HTTP was not correctly being redirected to HTTPS by Netlify on first load on a fresh cache.
When building with new @next.55, my _redirect file is being copied over, but it is not including the necessary
* /.netlify/functions/render 200
, which seems to be needed to render the entire app. It seems to work correctly if you have no pre-existing _redirect file.Reproduction
Add _redirect file to Static folder, and cry as your app is put into the magicians hat.
Logs
No response
System Info
Severity
serious, but I can work around it
Additional Information
No response
The text was updated successfully, but these errors were encountered: