{"version":"2.1.232","anchor":"webfetch-validates-redirect-targets-before-showing-them","canonical_anchor":"webfetch-validates-redirect-targets-before-showing-them","heading":"WebFetch validates redirect targets before showing them","tier":"notice","area":"WebFetch","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/webfetch-validates-redirect-targets-before-showing-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### WebFetch validates redirect targets before showing them\n\nRedirected fetches now tell you the page moved and was not fetched for you automatically.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Non-http(s) destinations are withheld entirely.\n- Over-long URLs are truncated with a note; hostnames longer than a valid DNS name are flagged as unfetchable.\n- Only a clean, complete destination gets the follow-up instruction to call WebFetch again with those parameters.\n\n**Evidence**\n\n`REDIRECT DETECTED: The URL redirects to a location that was not fetched automatically.`\n\n- Area: WebFetch\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}