Skip to content

Set "User-Agent" header for requests to LAVA server - #38

Merged
sjoerdsimons merged 1 commit into
collabora:mainfrom
pawiecz:set-user-agent
Nov 10, 2026
Merged

sjoerdsimons merged 1 commit into
collabora:mainfrom
pawiecz:set-user-agent

Conversation

@pawiecz

@pawiecz pawiecz commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator

Having this header unset may lead to request rejection if a LAVA server is behind a scraper protection service such as Anubis.

Fixes: #37

Having this header unset may lead to request rejection if a LAVA server
is behind a scraper protection service such as Anubis.

Signed-off-by: Paweł Wieczorek <pawiecz@collabora.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are reported for the change adding a default User-Agent header to LAVA API requests.

No open issues 🎉

What changed in this PR

Adds a default User-Agent header to LAVA API requests, addressing issue #37 by helping avoid rejection by scraper-protection services.

Changes:

  • Sets the header to the Cargo package name and version (name/version).
  • Preserves the existing redirect policy and default headers.
File Description
lava-api/​src/​lib.rs Configures the HTTP client’s default User-Agent header.

Review effort: Balanced

@sjoerdsimons
sjoerdsimons added this pull request to the merge queue Nov 10, 2026
Merged via the queue into collabora:main with commit a8b619e Nov 10, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Requests don't set "User-Agent" header

3 participants