| Summary: | Assertion in disk cache code with redirect to a non-http resource | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Antti Koivisto <koivisto> | ||||
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | ap, commit-queue | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Antti Koivisto
2015-02-16 06:53:18 PST
Created attachment 246650 [details]
patch
Comment on attachment 246650 [details] patch Clearing flags on attachment: 246650 Committed r180148: <http://trac.webkit.org/changeset/180148> All reviewed patches have been landed. Closing bug. Comment on attachment 246650 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=246650&action=review > Source/WebKit2/NetworkProcess/cache/NetworkCache.cpp:265 > + if (!originalRequest.url().protocolIsInHTTPFamily() || !response.isHTTP()) { This "in HTTP family" vs. "HTTP" naming is quite misleading. How so? The reason for the lengthy "protocolIsInHTTPFamily" name is that it makes it clearer that it includes HTTPS. "isHTTP" doesn't make that clear, and when in the same line with "protocolIsInHTTPFamily" in particular, it actively hints that it doesn't include https, which is untrue. URLs and responses are quite different types of objects though. To me it seems clear that an "HTTP response" covers HTTPS too (there is no NSHTTPSURLResponse either). > URLs and responses are quite different types of objects though
What is the difference? Both are used for arbitrary URLs, there is no difference at all.
I see your reference to Foundation naming scheme, however it's not a fair comparison, those names are ancient, and they don't need to play well with naming in WebKit.
In any case, patches are welcome if you have naming improvements. |