Simon Zünd db5dcc9f1a [e2e] Load DevTools on a different origin than the target page ...

This CL changes e2e tests to load the DevTools frontend on the
'devtools-frontend.test' origin instead of using 'localhost'.
'localhost' is used by the target page. If we also load DevTools via
'localhost' than the two pages share window.localStorage and are
considered "same-origin", which hardly reflects reality.

To enable this CL, we have to change the hosted-mode server to set
some CORS headers. More specifically, we allow the DevTools frontend
to request arbitray resources from the hosted-mode server, while
target pages have to be explicit in their ".headers" or
".rawresponse" files.

The CL also rebaselines a couple of e2e test that expect exact
response sizes or expect exact response headers.

R=jacktfranklin@chromium.org, pfaffe@chromium.org

Bug: 1297458
Change-Id: Ie18069e2effcc53cfd10a19296dc5d5c74b40e17
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3467975
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
Reviewed-by: Philip Pfaffe <pfaffe@chromium.org>
Commit-Queue: Simon Zünd <szuend@chromium.org>

2022-02-16 12:43:57 +00:00

..

BUILD.gn

[e2etest] Move hosted mode server to https

2020-11-18 12:58:43 +00:00

cert.pem

[e2etest] Move hosted mode server to https

2020-11-18 12:58:43 +00:00

key.pem

[e2etest] Move hosted mode server to https

2020-11-18 12:58:43 +00:00

server.js

[e2e] Load DevTools on a different origin than the target page

2022-02-16 12:43:57 +00:00