64e4a9b0eb
Motivation: When using client-certificates on a website on port `443`, we would normalise the user input with `new URL` but still generate a "bad" representation of the "origin" internally, since the just do concatenated "host:port". (The origin doesn't contain the port in case of :443) We use `clientCertificatesToTLSOptions` in two places: a) for APIRequestContext, there we pass one from the URL constructor over and b) from the socks proxy, there we **now** also pass a "good one" over. Test plan: We don't want to run the tests on port :443, so only manually validated the fix. Relates https://github.com/microsoft/playwright/issues/31906 |
||
|---|---|---|
| .. | ||
| bin | ||
| bundles | ||
| src | ||
| types | ||
| .eslintrc.js | ||
| .npmignore | ||
| browsers.json | ||
| cli.js | ||
| index.d.ts | ||
| index.js | ||
| index.mjs | ||
| package.json | ||
| README.md | ||
| ThirdPartyNotices.txt | ||
playwright-core
This package contains the no-browser flavor of Playwright.