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

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 

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