Repository navigation
Follow public redirects when checking chat links - #225
Merged
Merged
Conversation
Owner
Author
|
Prompt roles, partials, rendering data, and the stable-prefix/dynamic-packet layout are unchanged. The added sentence requires a successful crawl result before calling a page read. The public prompt behavior changes intentionally; workspace prompt rendering and LLM contract tests passed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A direct request to verify a Mozilla page failed because
crawl_urlrejected its ordinary HTTP 301 response. Follow up to five HTTP redirects, validating and pinning every destination again. One deadline covers DNS, all requests, and body reads. Keep private-network, credentialed-URL, proxy, binary-body, and decoded-size restrictions.Clarify that search results alone do not mean a page was read. The SAFE probe previously acknowledged a failed crawl but then labelled the search result as a read page.
Validation: formatting and diff checks, 2466 workspace tests passed (10 ignored), all-target Clippy with warnings denied. Redirect tests cover relative locations, supported statuses, the hop limit, missing or invalid locations, and private or unsupported destinations. The same live Mozilla crawl failed with 301 before the change and returned Firefox page text after it.