You'll notice
Useful2 Signal1
Redirected fetches now tell you the page moved and was not fetched for you automatically.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a fetch redirects, WebFetch now parses and checks the destination before relaying it, and says the page was at a location that was not fetched automatically rather than that it redirects to a different host.
Details
- Non-http(s) destinations are withheld entirely.
- Over-long URLs are truncated with a note; hostnames longer than a valid DNS name are flagged as unfetchable.
- Only a clean, complete destination gets the follow-up instruction to call WebFetch again with those parameters.
Evidence
REDIRECT DETECTED: The URL redirects to a location that was not fetched automatically.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Data-loss-prevention blocks are marked separately from fetch failures
Both mention fetch
-
v2.1.236
Web fetch agent switch moved into per-host state
Both mention fetch