Show redirected links
See original GitHub issueToday gaxios quietly follows redirects. Folks may want to see this as a warning, so we should show that info and give an option to make that show up as an error.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
WhereGoes: Tiny URL Expander | Redirect Checker
It will show you the full redirection path of URLs, shortened links, or tiny URLs. Also referred to as a link checker, url...
Read more >Redirect Detective - Discover where those redirects really go to
Display redirects in full. Redirect Detective is a free URL redirection checker that allows you to see the complete path a redirected URL...
Read more >Redirect Checker | Check your Statuscode 301 vs 302
Check your URL redirect for accuracy. Our Redirect Checker will analyse all redirections. Try Now!
Read more >Redirect Tracker | Status and Redirect code Tracker
The redirect checker for URL follows the route of any given URL. It shows a complete redirected URL's path, tiny URL's or shortened...
Read more >Redirect Checker | Check the redirection of URLs
Redirect checker tool allows you to get insight on URL redirect. Check if a requested URL is redirected and to analyze its redirect...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

👋 I realize this issue is a bit old, but I wanted to chime in with a use case for failing or even detecting 301/2 redirects with linkinator.
We use linkinator to find busted links across a large-ish docs site. There’s an internal redirect map/middleware for old known paths forwarding to new paths. We often used these deprecated paths internally in the docs. Ideally those internal links would be discoverable so they can be updated to the newer path and not require a hit to the redirect middleware.
It seems that when Linkinator follows 301 redirects and finds relative paths, it assumes that the path is relative to the original URL, however in the cases where the domain has changed it seems to be detecting 404s for URLs that are otherwise valid.