- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 12 Dec 2008 11:13:29 +1100
- To: HTTP Working Group <ietf-http-wg@w3.org>
It seems like there's pretty strong support for removing multipart/ related as a message delimiter (I.e., removing RFC2616 section 4.4, bullet #4). However, I want to move carefully here, because this is a change at a very low level, with potentially far-reaching effects. To that end, could folks who have implementations, or have tested them, please fill out the implementation spreadsheet; http://spreadsheets.google.com/ccc?key=pAZLaupBqGqXrtsaexTjPYg&hl=en I've added an appropriate column on the clients, intermediaries and servers sheets. (if you can't or don't have time to post to the spreadsheet, please send to the list). Cheers, On 12/12/2008, at 4:17 AM, Jamie Lokier wrote: > Henrik Nordstrom wrote: >>> They aren't used that way. I don't know of any implementation >>> that uses the multipart delimiter to find the end of body (they >>> use CL, chunked, or a closed connection). >> >> Hmm.. you may be right. On a closer inspection I see that I misread >> some >> of the data. Sorry for the confusion. >> >> So it looks like dropping 4.4 §4 entirely may be an option. > > If it's possible to drop support for multipart/byterange delimited > messages, because it's not used anyway, that would be a really good > thing imho. It's an ugly, pointless, unused and probably poorly > implemented complication in message parsers. > > -- Jamie -- Mark Nottingham http://www.mnot.net/
Received on Friday, 12 December 2008 00:14:11 UTC