Skip to content

IE: diagnose ryo.lu proxy blocks (Cloudflare) + store docs#1012

Draft
ryokun6 wants to merge 2 commits intomainfrom
cursor/ryo-lu-browser-block-4aa5
Draft

IE: diagnose ryo.lu proxy blocks (Cloudflare) + store docs#1012
ryokun6 wants to merge 2 commits intomainfrom
cursor/ryo-lu-browser-block-4aa5

Conversation

@ryokun6
Copy link
Copy Markdown
Owner

@ryokun6 ryokun6 commented Mar 19, 2026

Summary

  • api/iframe-check: When upstream returns HTTP 403 and Cloudflare signals (cf-mitigated or server: cloudflare), respond with type: cloudflare_challenge and clearer message / details so DevTools and the IE error UI explain server-side fetch limits.
  • useInternetExplorerStore: Document why bare ryo.lu is not in DIRECT_PASSTHROUGH_DOMAINS (X-Frame-Options) and that proxy fetch can still fail on CF.

Root cause (manual investigation)

  • https://ryo.lu is loaded in “current” mode via /api/iframe-check (not direct iframe) because it cannot be embedded cross-origin from os.ryo.lu when the site sends X-Frame-Options: SAMEORIGIN.
  • Server-side curl -sSIL https://ryo.lu from CI-like environments returns 403 with cf-mitigated: challenge, so the proxy cannot retrieve HTML for embedding.

Testing

  • bun run build
Open in Web Open in Cursor 

@ryos-deploy
Copy link
Copy Markdown

ryos-deploy bot commented Mar 19, 2026

The preview deployment for ryos-dev is ready. 🟢

Open Preview | Open Build Logs | Open Application Logs

Last updated at: 2026-03-19 15:00:18 CET

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants