Repository navigation
Fix web_profile_info returning HTML instead of JSON - #325
Merged
Merged
Conversation
The manual fallback request used the legacy i.instagram.com host, which now responds with an HTML page, so parsing failed with "Unexpected token '<', "<!DOCTYPE "... is not valid JSON". Use www.instagram.com (the host Instagram's own web client uses) and accept either host when intercepting the response. Also validate the HTTP status and content type before parsing, so a 429 or login/challenge page produces a clear error mentioning the status instead of a cryptic SyntaxError. Fixes #324, related #312 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BFDJvmX31k6Xd82sRL7meF
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.
The manual fallback request used the legacy i.instagram.com host, which now responds with an HTML page, so parsing failed with "Unexpected token '<', "<!DOCTYPE "... is not valid JSON". Use www.instagram.com (the host Instagram's own web client uses) and accept either host when intercepting the response.
Also validate the HTTP status and content type before parsing, so a 429 or login/challenge page produces a clear error mentioning the status instead of a cryptic SyntaxError.
Fixes #324, related #312
Claude-Session: https://claude.ai/code/session_01BFDJvmX31k6Xd82sRL7meF