Fix recipe preview failures with Firecrawl fallback#58
Merged
Conversation
…rors Many recipe sites (allrecipes.com, etc.) use Cloudflare bot protection that blocks direct HTTP fetch, returning 402/403 or a JS challenge page. This adds a Firecrawl API fallback for blocked sites, User-Agent headers on requests, Cloudflare challenge detection, and structured ExtractionError responses so the frontend can show actionable guidance instead of generic 500 errors. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
4 tasks
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1072daf1cf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Previously all non-200 statuses triggered the Firecrawl fallback, causing misleading site_blocked errors for ordinary server failures. Now only bot-block codes and Cloudflare challenges route to Firecrawl; other non-200 responses return fetch_failed instead. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.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
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
User-Agentheader to outbound recipe fetch requestsExtractionErrorresponses with machine-readable error codes (site_blocked,not_found,fetch_failed) instead of generic 500sFIRECRAWL_API_KEYenv var (optional) andfirecrawl_json_ld/firecrawl_haikuextraction method constantsHTTPFetchOverride,FirecrawlFetchOverride) for fully offline testingTest plan
site_blocked, 404+not_foundFIRECRAWL_API_KEYin ECS task definition🤖 Generated with Claude Code