The article is good for one-off debugging (curl is my personal favorite). For continuous monitoring, we at Heii On-Call just last week released website monitoring to assert an HTTP response status code plus Location header [1], and have some best practices for redirect monitoring for anyone with a website which will be published next week.
FYI these features were requested by a user who signed up from HN a few weeks ago and wanted to monitor these redirects in addition to their homepage. Hope that helps.
[1] https://heiioncall.com/blog/your-probes-your-rules-expected-...
If you can use chrome, then use this one, best I have found in my travels - https://chrome.google.com/webstore/detail/redirect-path/
Other than that, I found this article really interesting - has gotten me into now exploring curl (especially after setting my pi 4 up as a mullvad vpn gateway with nextdns for my home network)
I think that was mentioned in the article too.
I quite often try to debug a 201 and the body is not retained in the Dev Tools, even with 'Preserve logs' turned on.
It particularly annoys me if you reload a page with a websocket open you see the logs for the websocket closing right at the start of the subsequent load. (Preserve logs is off of course)
There are multiple decades old bugzilla discussions about Firefox's idiosyncratic websocket lifecycle handling. Not sure exactly which causes this, doesn't seem to be much point in debugging further
This is especially useful in the funnest kind of cases where you have mutual recursion or other types of loops.
