Parsing Content-Type headers with parameters may fail (4.0D)

To: www-lib-bugs@w3.org
Subject: Parsing Content-Type headers with parameters may fail (4.0D)
From: James Gallagher <jimg@dcz.cvo.oneworld.com>
Date: Wed, 29 May 1996 10:22:29 -0700
From jimg@dcz.cvo.oneworld.com Wed May 29 13: 22:40 1996
Message-Id: <31AC87D5.41C67EA6@dcz.cvo.oneworld.com>
Organization: The University of Rhode Island
Sender: jimg@dcz.cvo.oneworld.com
X-List-URL: http://www.w3.org/pub/WWW/Archives/Public/www-lib-bugs/
X-Mailer: Mozilla 3.0b3 (X11; I; SunOS 4.1.3 sun4c)

Parsing a Content-Type header with an optional parameter may fail; the 
parameter is ignored if there is a space between the type/subtype
part of the header and the parameter.

For example, given:

    Content-Type: multipart/mixed;boundary=<blah, blah>

The `boundary' parameter is properly recorded in the request object.
However, adding a space between the `;' and `boundary' causes the parameter 
to be ignored:

    Content-Type: multipart/mixed; boundary=<blah, blah>

To reproduce, use a debugger and set a break point in HTMIME.c:parseheader.

Sorry, but I do not have a fix. It looks like the problem occurs in 
HTSocket.c:HTReadSocket.
-- 
__________________________________________________________________________

James Gallagher		         The Distributed Oceanographic Data System
jgallagher@gso.uri.edu                            http://dods.gso.uri.edu/

Prev: Problems with the nntp url!!!!
Next: Re: Automake 0.32
Index: Message index of www-lib-bugs@w3.org mailing list
Thread: Thread index of www-lib-bugs@w3.org mailing list