🤖 fix: improve web_fetch HTTP error reporting with body parsing #747
Conversation
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
- Parse and include HTTP status code (e.g., 'HTTP 404' instead of 'HTTP error 4xx/5xx') - Include parsed error page content when available (e.g., 404 pages) - Detect Cloudflare challenge pages and show clear error message - Refactor response parsing into reusable helper functions - Add tests for HTTP 404 handling and Cloudflare detection _Generated with mux_
ammario
approved these changes
Nov 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Improves error messages when
web_fetchencounters HTTP 4xx/5xx responses:HTTP status code in error: Shows actual status code (e.g.,
HTTP 404) instead of genericHTTP error (4xx/5xx)Parsed error body: When the server returns an error page (like a 404), we now parse and include its content so the AI can understand what went wrong
Cloudflare detection: Detects Cloudflare JS challenge pages and shows a clear error:
Cloudflare security challenge (page requires JavaScript)Example Outputs
Before:
After:
Or for Cloudflare-protected sites:
Testing
Generated with
mux