Bug 215604 - parsing on invalid Content-Type fields inconsistent
Summary: parsing on invalid Content-Type fields inconsistent
Status: RESOLVED MOVED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: Safari 13
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: http://test.greenbytes.de/tech/tc/htt...
Keywords: BrowserCompat, InRadar
Depends on:
Blocks: 192000
  Show dependency tree / graph
 
Reported: 2020-08-18 05:16 PDT by Julian Reschke
Modified: 2023-11-13 15:20 PST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julian Reschke 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.
Comment 1 Radar WebKit Bug Importer 2020-08-25 05:17:18 PDT 
<rdar://problem/67732394>
Comment 2 Ahmad Saleem 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".