Jina Reader: GET drops URL fragments, and 200 can still carry a warning

Jina Reader: GET drops URL fragments, and 200 can still carry a warning

TL;DR

With the Jina Reader API, use POST so URL fragments survive, and check the warning field on every 200 response. A successful HTTP status from the Reader only means the Reader answered, not that the target page did. Context: From a community Jina skill guide.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Two gotchas. Always use POST to the reader endpoint rather than the GET URL-prefix form, because GET silently drops URL fragments and breaks single-page-app URLs that depend on them. And the Reader returns HTTP 200 even when the target site errored (for example a 404): a non-empty warning field in the response is the real signal that something went wrong.

Source: From a community Jina skill guide. Two gotchas. Always use POST to the reader endpoint rather than the GET URL-prefix form, because GET silently drops URL fragments and breaks single-page-app URLs that depend on them. And the Reader returns HTTP 200 even when the target site errored (for example a 404): a non-empty warning field in the response is the real signal that something went wrong.

Verified resolution: With the Jina Reader API, use POST so URL fragments survive, and check the warning field on every 200 response. A successful HTTP status from the Reader only means the Reader answered, not that the target page did.

Source URL: https://github.com/chrisliu298/dotfiles/blob/HEAD/agents/skills/jina/SKILL.md