Bug#516667: [HTTP::Request::Common] MIME boundary value definition

[Damyan Ivanov]

-=| Lux In Tenebris, Mon, Feb 23, 2009 at 02:22:03AM +0300 |=-
> Package: libwww-perl
> Version: 5.820-1
> 
> Does the way it defines MIME multipart boundary values in Content-Type
> header is much compatible? While LWP is always setting something like:
> Content-Type: multipart/form-data;
> boundary=GTXZ7WqgwvYfDGRBbLlgTxQIWXsMmlXOvrD6pDEe, I've noted that
> many other applications are using hyphens prefixed boundary values in
> the header.
> I've faced this incompatiblity (?) when writing LWP based RapidShare
> upload script, RS server software persistently denies any POST
> requests with LWP's boundary values.
> 
> Citing section 7.2.1 of RFC 1341
> (http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html):
> ===
> The Content-Type field for multipart entities requires one parameter,
> "boundary", which is used to specify the encapsulation boundary. The
> encapsulation boundary is defined as a line consisting entirely of two
> hyphen characters ("-", decimal code 45) followed by the boundary
> parameter value from the Content-Type header field.

As far as I see, the boundary part in Content-Type doesn't have to 
start with two hyphens, only the real boundary used in the request 
body shall.

Can you verify if the actual boundary used has indeed no hyphens?

-- 
dam            JabberID: dam at jabber.minus273.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20090223/5a05c666/attachment.pgp