| commit | 505f1ff2ce0cfd4abbf6c96294cc3af2a6d27481 | [log] [tgz] |
|---|---|---|
| author | Jonathan Hao <phao@chromium.org> | Thu Mar 02 14:54:42 2023 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Mar 02 16:20:42 2023 |
| tree | f725b402ab879c0d55cb46bfec7d4d2c7addeafc | |
| parent | 46e1750aa994319806887d7896d43f119ba05c7d [diff] |
[Private Network Access] Test redirect from same origin to cross origin At [1], a concern was raised about the implementation that allows secure same-origin private network requests without preflights. There was a possibility that redirects were not correctly handled. The above bug was fixed in [2], but it's still good to add some tests. The test cases added in this CL test redirects from same-origin to cross-origin or vice versa. Failed tests in virtual/lna-allow-potentially-trustworthy-same-origin are expected, because when PrivateNetworkAccessAllowPotentiallyTrustworthySameOrigin is enabled. This CL also removes the UUID from the response body because it prevents UUID from going into the expected output. [1] https://chromium-review.googlesource.com/c/chromium/src/+/4221658/comment/ca7f33a7_1599ae6f/ [2] https://chromium-review.googlesource.com/c/chromium/src/+/4287225 Bug: 1382068 Change-Id: I96352dcba7c7c6517aac0108d24e1fa0491aacbe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272862 Commit-Queue: Jonathan Hao <phao@chromium.org> Reviewed-by: Titouan Rigoudy <titouan@chromium.org> Cr-Commit-Position: refs/heads/main@{#1112203}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune (or git fetch -p && git merge).
See the documentation website and in particular the system setup for running tests locally.
The wpt command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve - For starting the wpt http serverwpt run - For running tests in a browserwpt lint - For running the lint against all testswpt manifest - For updating or generating a MANIFEST.json test manifestwpt install - For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave - For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt commands must be prefixed with python or the path to the python binary (if python is not in your %PATH%).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic../wpt lint as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!