Re: wget 1.11 alpha1 - content disposition filename
Zitat von Hrvoje Niksic <[EMAIL PROTECTED]>: > Jochen Roderburg <[EMAIL PROTECTED]> writes: > > > E.g, a file which was supposed to have the name B&W.txt came with the > header: > > Content-Disposition: attachment; filename=B&W.txt; > > All programs I tried (the new wget and several browsers and my own script > ;-) > > seemed to stop parsing at the first semicolon and produced the filename > B&. > > Unfortunately, if it doesn't work in web browsers, how can it be > expected to work in Wget? The server-side software should be fixed. > I mainly wanted to hear from some "HTTP/HTML-Experts" that I was correct with my assumption that the problem here is at the server side ;-) Thank you, Mauro and Hrvoje, for confirming that. Regards, J.Roderburg
Re: wget 1.11 alpha1 - content disposition filename
Jochen Roderburg <[EMAIL PROTECTED]> writes: > E.g, a file which was supposed to have the name B&W.txt came with the header: > Content-Disposition: attachment; filename=B&W.txt; > All programs I tried (the new wget and several browsers and my own script ;-) > seemed to stop parsing at the first semicolon and produced the filename B&. Unfortunately, if it doesn't work in web browsers, how can it be expected to work in Wget? The server-side software should be fixed.
Re: wget 1.11 alpha1 - content disposition filename
Jochen Roderburg ha scritto: Hi, I was happy to see that a long missed future was now implemented in this alpha, namely the interpretaion of the filename in the content dispostion header. Just recently I had hacked a little script together to achieve this, when I wanted to download a greater number of files where this was used ;-) I had a few cases, however, which did not come out as expected, but I think the error is this time in the sending web application and not in wget. E.g, a file which was supposed to have the name B&W.txt came with the header: Content-Disposition: attachment; filename=B&W.txt; the error is definitely in the web application. the correct header would be: Content-Disposition: attachment; filename="B&W.txt"; All programs I tried (the new wget and several browsers and my own script ;-) seemed to stop parsing at the first semicolon and produced the filename B&. Any thoughts ?? i think that the filename parsing heuristics currently implemented in wget are fine. you really can't do much better in this case. -- Aequam memento rebus in arduis servare mentem... Mauro Tortonesi http://www.tortonesi.com University of Ferrara - Dept. of Eng.http://www.ing.unife.it GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget Deep Space 6 - IPv6 for Linuxhttp://www.deepspace6.net Ferrara Linux User Group http://www.ferrara.linux.it
wget 1.11 alpha1 - content disposition filename
Hi, I was happy to see that a long missed future was now implemented in this alpha, namely the interpretaion of the filename in the content dispostion header. Just recently I had hacked a little script together to achieve this, when I wanted to download a greater number of files where this was used ;-) I had a few cases, however, which did not come out as expected, but I think the error is this time in the sending web application and not in wget. E.g, a file which was supposed to have the name B&W.txt came with the header: Content-Disposition: attachment; filename=B&W.txt; All programs I tried (the new wget and several browsers and my own script ;-) seemed to stop parsing at the first semicolon and produced the filename B&. Any thoughts ?? Best Regards, Jochen Roderburg ZAIK/RRZK University of Cologne Robert-Koch-Str. 10Tel.: +49-221/478-7024 D-50931 Koeln E-Mail: [EMAIL PROTECTED] Germany
