fix(api): return 403 for anti-bot blocked results in /md and /llm endpoints - #2185
Open
Battleplus wants to merge 1 commit into
Open
fix(api): return 403 for anti-bot blocked results in /md and /llm endpoints#2185Battleplus wants to merge 1 commit into
Battleplus wants to merge 1 commit into
Conversation
…points Both handle_markdown_request and handle_llm_qa promoted any unsuccessful crawl into HTTP 500. Since 0.8.5, is_blocked() sets success=False with error_message 'Blocked by anti-bot protection: <reason>', so Cloudflare- protected sites returned opaque 500 instead of a client-meaningful error. Differentiate anti-bot failures (403) from genuine server errors (500) by inspecting the error message for 'blocked' / 'anti-bot' keywords. Fixes unclecode#2116 Signed-off-by: Battleplus <3559424769@qq.com>
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
1 participant
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
Both
handle_markdown_requestandhandle_llm_qaindeploy/docker/api.pypromoted any unsuccessful crawl into HTTP 500. Since 0.8.5,is_blocked()setssuccess=Falsewitherror_message = "Blocked by anti-bot protection: <reason>", so Cloudflare-protected sites returned opaque 500 instead of a client-meaningful error.This PR differentiates anti-bot failures (403) from genuine server errors (500) by inspecting the error message for
blocked/anti-botkeywords.Changes
deploy/docker/api.py: In bothhandle_markdown_requestandhandle_llm_qa, checkresult.error_messagefor anti-bot keywords before deciding status code.Test plan
POST /mdwith a Cloudflare-protected URL → should return 403 with "Blocked by anti-bot protection" detailPOST /llm/{url}with a Cloudflare-protected URL → should return 403POST /mdwith a genuinely broken URL → should still return 500Fixes #2116