PLAYWRIGHT 1.65 STOPPED SENDING PROXY CREDENTIALS TO WEBSITES
proxy option now answer only proxy challenges and are no longer sent to websites. OURS: a Proxies.sx gateway credential belongs in the proxy fields and nowhere else, which is how our Playwright guide already passes it. Jump to what to do.WHAT CHANGED
ESTABLISHED: The Playwright 1.65 release notes on playwright.dev list this line under the heading Breaking Changes
(the GitHub release files the same line under Notable Changes
): Proxy credentials are no longer sent to websites. The credentials in the proxy option now answer only proxy challenges. To authenticate on a website, use httpCredentials.
The GitHub release for v1.65.0 carries the publication time 2026-11-05T18:25:45Z; v1.65.1 followed on 2026-11-13T21:46:58Z.
ESTABLISHED: The same list says Cookie matching now follows RFC 6265.
A run that reads cookies by URL after upgrading can see a different set than before; the release note gives the cases.
SOURCE AND HOW IT WAS CHECKED
ESTABLISHED: Both sentences were read on 17 November 2026 in two places published by the Playwright project: the release notes page on playwright.dev and the body of the v1.65.0 release on GitHub. The wording of both sentences matches in both; the heading above them differs as noted. This is one vendor describing its own software, so it counts as a single source. We did not run 1.65 to observe the behaviour.
WHY IT MATTERS
ESTABLISHED: HTTP keeps the two kinds of authentication apart. RFC 9110 defines 407 as the status that indicates that the client needs to authenticate itself in order to use a proxy for this request
, answered with Proxy-Authorization, a field that applies only to the next inbound proxy that demanded authentication
. A website asks with 401 and WWW-Authenticate and is answered with Authorization. From 1.65 Playwright states that the proxy credentials serve the first case only.
ESTABLISHED: Read with the release note, this has two sides. A script that relied on the proxy credentials also being offered to a website has to supply httpCredentials from 1.65. And, by the note, the proxy credential is no longer sent to websites.
WHAT AN AGENT SHOULD DO
- ESTABLISHED: Read the installed version before a run:
npx playwright --version. The change applies from 1.65.0. - ESTABLISHED: If a target site needs HTTP authentication, pass it in
httpCredentialson the context. Keep the proxy login inproxy.usernameandproxy.password. - ESTABLISHED: Read the status before changing anything: 407 is the proxy asking, 401 is the site asking. They need different credentials.
- OURS: Our Playwright guide passes the gateway credential as
proxy: { server: "http://gw.proxies.sx:7000", username, password }, with the noteseparate field: never put it in a URL
. That form needs no change for 1.65. Guide: /integrations/playwright/. - OURS: A 407 from our gateway carries
E_AUTH_REQUIRED(noProxy-Authorizationheader) orE_AUTH_INVALID(credentials rejected). A connection refused with anE_code is free. Table: /errors.md. Username format, country and session id: /pool/skill.md.
HONEST CAVEATS
- ESTABLISHED: the statement is the vendor's release note, read at the source. We did not test 1.65 against any site or proxy, ours included.
- ESTABLISHED: the note does not say which earlier versions sent the credentials to websites, or under which conditions.
- OURS: nothing here changes whether a site accepts a request. A proxy sets where a request comes from; the site's own rules still apply.
VERIFY IT YOURSELF
- Playwright release notes, version 1.65 (read 17 November 2026): playwright.dev/docs/release-notes
- GitHub release v1.65.0, published 2026-11-05 (read 17 November 2026): microsoft/playwright v1.65.0 · v1.65.1
- RFC 9110 (read 17 November 2026): §15.5.8 407 · §11.7.2 Proxy-Authorization · §15.5.2 401
- Proxies.sx contracts (our claims, read 17 November 2026): /integrations/playwright/ · /errors.md · /pool/skill.md
Ground Truth · back to the feed · machine-readable: /news/feed.md