DevTools: Network.requestWillBeSent and Network.requestIntercepted report different urls |
|||
Issue descriptionChrome: M62 Sometimes either of the events report encoded URL, whereas the other one doesn't: 1. Network.requestWillBeSent encodes URL, whereas Network.requestIntercepted doesn't. 2. Network.requestWillBeSent does not encode URL, whereas Network.requestIntercepted does. Observed with puppeteer: https://github.com/GoogleChrome/puppeteer/issues/558 I'll post reduced reproes shortly.
,
Oct 4 2017
,
Oct 21 2017
The following user scenario: 1. Consider request interception is enabled with protocol's setRequestInterceptionEnabled call 2. Consider a page that issues a request to the URL with query string: <img src='http://foo.com/img.png?hello|world'></img> 3. The protocol will issue two events, each dispatching the request's URL - RequestWillBeSent - URL: http://foo.com/img.png?hello|world - requestIntercepted - URL: http://foo.com/img.png?hello%7Cworld Notice that requestIntercepted dispatched encoded URL. The reason is the difference in GURL and KURL. GURL canonicalizes the URL, whereas KURL don't. In this specific example, the '|' symbol is canonicalized as a part of query string.
,
Dec 27 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by lushnikov@chromium.org
, Aug 27 2017