This is a follow up #29564 I did a deep dive on a redirect issue I observed in my infrastructure and originally attributed to some configuration mistakes on my part. I have code hosted on `example.com/code` and use subdomain proxying. This leads to the uimode being exposed on `example.com/code/proxy/{{port}}`. Clicking on the open uimode link shown by vscode redirected with a 302 to `example.com/proxy/{{port}}` The absolute redirect url overruled the relative path handling reverse proxies rely on. This PR turns the absolute into a relative url to avoid this issue. |
||
|---|---|---|
| .. | ||
| 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.