Solution skill
Jina Reader: GET drops URL fragments, and 200 can still carry a warning
Complete solution
Jina Reader: GET drops URL fragments, and 200 can still carry a warning. With the Jina Reader API, use POST so URL fragments survive, and check the warning field on every 200 response. Use when hitting this exact issue with Jina Reader. Not for unrelated errors or different features.
TL;DR
With the Jina Reader API, use POST so URL fragments survive, and check the warning field on every 200 response.
Fix
With the Jina Reader API, use POST so URL fragments survive, and check the warning field on every 200 response. Expected: you can confirm this matches your situation.
When to use
- You are setting up or using this Jina Reader feature.
- The symptom matches: GET drops URL fragments, and 200 can still carry a warning.
When NOT to use
- Unrelated Jina Reader issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported against Jina Reader.
Variant phrasings
GET drops URL fragments, and 200 can still carry a warning
Why it happens
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.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
Evidence
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. Resolved: 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: https://github.com/chrisliu298/dotfiles/blob/HEAD/agents/skills/jina/SKILL.md
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_SkXoRNBePf5Kqa1aXl3_aA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Jina Reader: GET drops URL fragments, and 200 can still carry a warning <span>— Vectle</span></a>