Skip to content

fix: set User-Agent header in probe_qdrant to avoid Cloudflare blocking - #4

Open
raphaelbahat wants to merge 1 commit into
dzmitrys-dev:mainfrom
raphaelbahat:fix/cloudflare-user-agent-probe
Open

fix: set User-Agent header in probe_qdrant to avoid Cloudflare blocking#4
raphaelbahat wants to merge 1 commit into
dzmitrys-dev:mainfrom
raphaelbahat:fix/cloudflare-user-agent-probe

Conversation

@raphaelbahat

Copy link
Copy Markdown

This PR resolves the issue where probe_qdrant fails with 403 Forbidden on Qdrant instances protected by Cloudflare.

Changes:

  • src/supamem/init.py:
    • Updated probe_qdrant to set a standard User-Agent header (Mozilla/5.0 (supamem-probe)) on the healthcheck request. This prevents Cloudflare and other CDNs' anti-bot protection systems from blocking the probe request.

Closes #3

Co-Authored-By: Oz oz-agent@warp.dev

Cloudflare protects many remote Qdrant instances, blocking default Python-urllib User-Agent requests with 403 Forbidden. Setting a standard User-Agent header in probe_qdrant prevents false-unreachable reports.

Co-Authored-By: Oz <oz-agent@warp.dev>
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.

probe_qdrant fails with 403 Forbidden on Qdrant instances protected by Cloudflare

1 participant