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
First of all, thank you for creating such a useful tool. It has saved us countless hours, and has increased the quality of our documentation website for our open source software. 🙏
We have two NextJs sites which use redirects in the root page. The first does this to redirect to a default locale (/en), and the second does this to redirect to a /dashboard route.
No matter if I use a temporary redirect (307) or permanent redirect (308) these requests are always flagged as broken by linkinator. My understanding of the HTTP spec is that 3xx codes are not to be treated as errors, but that the request may require further action on the part of the browser. I therefore believe linkinator should determine if the 3xx code is flagged as broken based on if the URL that is redirected to ultimately results in a 2xx code.
Alternatively, it would be great to have a simple option to not treat redirects as broken via a CLI flag.
I am happy to work on this if you let me know where to start.
Hello!
First of all, thank you for creating such a useful tool. It has saved us countless hours, and has increased the quality of our documentation website for our open source software. 🙏
We have two NextJs sites which use redirects in the root page. The first does this to redirect to a default locale (
/en
), and the second does this to redirect to a/dashboard
route.No matter if I use a temporary redirect (307) or permanent redirect (308) these requests are always flagged as broken by linkinator. My understanding of the HTTP spec is that 3xx codes are not to be treated as errors, but that the request may require further action on the part of the browser. I therefore believe linkinator should determine if the 3xx code is flagged as broken based on if the URL that is redirected to ultimately results in a 2xx code.
Alternatively, it would be great to have a simple option to not treat redirects as broken via a CLI flag.
I am happy to work on this if you let me know where to start.
Example domain for testing: https://fresco-sandbox.networkcanvas.com
Thanks again!
The text was updated successfully, but these errors were encountered: