| Summary: | REGRESSION (r173356): Safari can't install a profile, gets 'Download Failed error | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Antti Koivisto <koivisto> | ||||||
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | ap, commit-queue, mitz | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | 528+ (Nightly build) | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Attachments: |
|
||||||||
|
Description
Antti Koivisto
2014-10-18 14:16:09 PDT
Created attachment 240069 [details]
patch
Comment on attachment 240069 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=240069&action=review > Source/WebCore/platform/network/mac/ResourceResponseMac.mm:69 > + [headerDictionary setObject:(NSString *)m_mimeType forKey:@"Content-Type"]; This can result in lying to the API client about the content of the response headers from the server. Can we use the -_setMIMEType: (which we use elsewhere in WebCore) instead? (In reply to comment #3) > Comment on attachment 240069 [details] > patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=240069&action=review > > > Source/WebCore/platform/network/mac/ResourceResponseMac.mm:69 > > + [headerDictionary setObject:(NSString *)m_mimeType forKey:@"Content-Type"]; > > This can result in lying to the API client about the content of the response > headers from the server. Can we use the -_setMIMEType: (which we use > elsewhere in WebCore) instead? /the -_setMIMEType:/the -_setMIMEType: method/ > This can result in lying to the API client about the content of the response
> headers from the server. Can we use the -_setMIMEType: (which we use
> elsewhere in WebCore) instead?
We probably can.
Created attachment 240073 [details]
patch 2
Comment on attachment 240073 [details] patch 2 Clearing flags on attachment: 240073 Committed r174866: <http://trac.webkit.org/changeset/174866> All reviewed patches have been landed. Closing bug. *** Bug 137493 has been marked as a duplicate of this bug. *** |