Skip to content

Send a standard browser Accept header for ad network homepage checks - #126

Merged
RaviTejaKNTS merged 1 commit into
mainfrom
ad-homepage-accept-header
Nov 13, 2026
Merged

RaviTejaKNTS merged 1 commit into
mainfrom
ad-homepage-accept-header

Conversation

@RaviTejaKNTS

Copy link
Copy Markdown
Collaborator

Problem

The ad network checker requests homepages with Accept: text/html,application/xhtml+xml. Browsers never send that exact value, and some site firewalls answer it with 403. From OVH, with the same stack127bot/1.0 user agent:

  • 350cc.com and 1teachmore.lk: 403 with the old header, 200 with the full page with the standard browser value (and with curl's */*).
  • 13milers.com: 403 either way.

In the production homepage-miss correction running now, about 40% of live checks are inconclusive. 14 of 15 sampled were http_status failures.

Change

  • Homepage requests send text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8.
  • The honest user agent is unchanged. The HTML content-type check after the fetch is unchanged, so non-HTML responses are still rejected. The ads.txt fetch keeps Accept: text/plain.

Checks

  • Ad network suite: 452 passed, 9 skipped.
  • npm run quality: 113 core tests passed.
  • Reviewed by a separate reviewer: no findings.

🤖 Generated with Claude Code

Some site firewalls answer 403 to the bare
"text/html,application/xhtml+xml" list, which browsers never send.
From OVH, with the same stack127bot user agent, 350cc.com and
1teachmore.lk return 403 to it and the full page to the standard
browser value. About 40% of live correction checks were inconclusive,
and 14 of 15 sampled were HTTP status failures. The user agent and the
HTML content-type check are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RaviTejaKNTS
RaviTejaKNTS merged commit b46ded0 into main Nov 13, 2026
4 checks passed

This branch was previously deployed

1 inactive deployment
production — 2039041c Deployed Nov 13, 2026 by RaviTejaKNTS via verify-production-build #117
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.

1 participant