Bug 215604

Summary: parsing on invalid Content-Type fields inconsistent
Product: WebKit Reporter: Julian Reschke <julian.reschke>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED MOVED    
Severity: Normal CC: ahmad.saleem792, mike, webkit-bug-importer
Priority: P2 Keywords: BrowserCompat, InRadar
Version: Safari 13   
Hardware: Unspecified   
OS: Unspecified   
URL: http://test.greenbytes.de/tech/tc/httpcontenttype/#multixmltextoneline
See Also: https://bugs.webkit.org/show_bug.cgi?id=192000
Bug Depends on:    
Bug Blocks: 192000    

Julian Reschke
Reported 2020-08-18 05:16:50 PDT
See <http://test.greenbytes.de/tech/tc/httpcontenttype/#multixmltextoneline> and <http://test.greenbytes.de/tech/tc/httpcontenttype/#multixmltexttwoline> (summaries). Webkit apparently handles Content-Type: x, y different from Content-Type: x Content-Type: y Both examples are invalid, but the fact that the outcome differs hints at inconsistent code with respect to re-combining field values. Note that both Firefox and Chrome show consistent behavior here.
Attachments
Radar WebKit Bug Importer
Comment 1 2020-08-25 05:17:18 PDT
Ahmad Saleem
Comment 2 2023-11-13 15:20:49 PST
Based on discussion on Slack with Alex, it is something to be fixed in CFNetwork. So marking this as "RESOLVED MOVED".
Note You need to log in before you can comment on or make changes to this bug.