## TL;DR

With the Jina Reader API, use POST so URL fragments survive, and check the warning field on every 200 response.

## Fix

1. 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.