[Webkit-unassigned] [Bug 192375] HTTPS Upgrade: Figure out if/how to tell clients that the HTTPS upgrade happened

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 10 14:51:47 PST 2018


--- Comment #33 from youenn fablet <youennf at gmail.com> ---
Note also that content blockers can potentially modify the URL.
For top level frames, we probably want to do this redirection.
This patch will fix that issue as well.

In terms of spec, we are trying to get closer to fetch.
The "upgrade" step is specified close to CSP checks for instance (https://fetch.spec.whatwg.org/#main-fetch) which this patch follows.

We cannot yet reunify NetworkLoadChecker and NetworkLoad because NetworkLoadChecker is used by NetworkResourceLoader and PingLoad, PingLoad using NetworkDataTask directly.

I would like to kill the current form of PingLoad and replace it with a 'keep alive' fetch.
At that point, we might be able to refactor NetworkLoadChecker/NetworkLoad relationship.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20181210/7b70c740/attachment.html>

More information about the webkit-unassigned mailing list