Re: [whatwg/fetch] Define the Content-Type header parser (#831)

domenic commented on this pull request.



> @@ -471,6 +685,9 @@ each other by 0x2C 0x20, in order.
      "<code>text/plain</code>", then return false.
     </ol>
 
+    <p class=warning>This intentionally does not use <a>extract a MIME type</a> as that algorithm is
+    rather forgiving and servers are not expected to implement it.

I still don't really understand. Why do we have a second parser on the client, to solve a client/server mismatch?

Maybe a better way to state this (either to help me understand here, or in the spec) would be with an example of what would go wrong if we used extract a MIME type.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/831#discussion_r235403796