tags 516667 upstream wontfix thanks -=| Lux In Tenebris, Mon, Feb 23, 2009 at 06:38:29PM +0300 |=- > 2009/2/23 Damyan Ivanov <[email protected]>: > > 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? > > I'm not talking about actual boundary used in a multipart message's > body, it's prefixed with 2 hyphens as it should. > But other popular applications like IE, Opera, CURL etc. are using > hyphens prefixed boundary values (is it for some compatibility > reasons?). > Few examples: > > === > POST /cgi-bin/upload.cgi?rsuploadid=153173063041207015 HTTP/1.1 > Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, > application/x-shockwave-flash, application/x-ms-application, > application/x-ms-xbap, application/vnd.ms-xpsdocument, > application/xaml+xml, application/vnd.ms-excel, application/msword, > */* > Content-Type: multipart/form-data; > boundary=---------------------------7d911535603fe > Accept-Encoding: gzip, deflate > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) > Host: rs460l3.rapidshare.com > Content-Length: 280464 > Connection: Keep-Alive > Cache-Control: no-cache > > -----------------------------7d911535603fe > Content-Disposition: form-data; name="filecontent"; filename="41742_182068.jpg > ===
As I see it, there is no requirement for the boundary value (in the header) to start with hyphens. Looks to me that rapidshare.com has to be fixed, not HTTP::Request::Common. This is why I am not very entusiastic on patching the Debian package and convincing upstream to apply the patch. If you feel otherwise (as it seems), please talk with upstream about it. Their request tracker is at http://rt.cpan.org/Public/Dist/Display.html?Name=libwww-perl Meanwhile, I am tagging this as wontfix. -- dam JabberID: [email protected]
signature.asc
Description: Digital signature
