Content-Disposition UTF-8 and filename problems

2008-03-08 Thread Todd Pattist
I'm having trouble with the filename after retrieving a php generated file download. It is retrieved with: http://site.com/download/file.php?id=62651 The content disposition header says: Content-Disposition: attachment; filename*=UTF-8''filename.zip I want it to end up as filename.zip, but it

Re: Content-Disposition UTF-8 and filename problems

2008-03-09 Thread Todd Pattist
, but it's in the right place. I believe someone else has seen this problem too (from the email archives IIRC). Thanks for a great program! Todd Pattist wrote: I'm having trouble with the filename after retrieving a php generated file download. It is retrieved with: http://site.com/download

Accept and Reject - particularly for PHP and CGI sites

2008-03-10 Thread Todd Pattist
I'm having trouble understanding how accept and reject work, particularly in the context of sites that rely on CGI and PHP to dynamically generate html pages. My questions relate to the following: 1) I don't fully understand the -A and -R effects and the difference, if any, between what links

Re: Accept and Reject - particularly for PHP and CGI sites

2008-03-10 Thread Todd Pattist
Thank you for the quick response. Background is I'm on Windows XP, Gnu wget 1.11 This "doesn't affect traversal of HTML files" functionality is currently implemented via a heuristic based on the filename extension. That is, if it ends in ".htm" or ".html", I believe, then it will be

Re: Accept and Reject - particularly for PHP and CGI sites

2008-03-10 Thread Todd Pattist
Todd Pattist wrote: Thank you for the quick response. Background is I'm on Windows XP, Gnu wget 1.11 This doesn't affect traversal of HTML files functionality is currently implemented via a heuristic based on the filename extension. That is, if it ends in .htm or .html, I believe

Re: Accept and Reject - particularly for PHP and CGI sites

2008-03-19 Thread Todd Pattist
Micah Cowan wrote: Well, -E is special, true. But in general the second quote is (by definition) correct. - -E, obviously, _shouldn't_ be special... I hope it's clear I'm not complaining. Wget is great and your efforts are very much appreciated. I just wanted to document the behavior I was

Re: Accept and Reject - particularly for PHP and CGI sites

2008-03-20 Thread Todd Pattist
When deciding whether it should delete a file afterwards, however, it uses the _local_ filename (relevant code also in recur.c, near "Either --delete-after was specified,"). I'm not positive, but this probably means query strings _do_ matter in that case. :p Confused? Coz I sure am!

Re: Accept and Reject - particularly for PHP and CGI sites

2008-03-20 Thread Todd Pattist
If we were going to leave this behavior in for some time, then I think it'd be appropriate to at least mention it (maybe I'll just mention it anyway, without a comprehensive explanation It would probably be sufficient to just add a very brief mention to the docs of 1.11, the two things

Re: Release: GNU Wget 1.11.1

2008-03-25 Thread Todd Pattist
Micah Cowan wrote: Announcing the release of version 1.11.1 of GNU Wget. ** Documentation of accept/reject lists in the manual's Types of Files section now explains various aspects of their behavior that may be surprising, and notes that they may change in the future. I'm glad to see that this

Re: [Bulk] Updates on Wget Future Directions

2008-04-01 Thread Todd Pattist
Micah Cowan wrote: Unccl svefg bs Ncevy, sbyxf. For greater clarity try: http://www.rot13.com/index.php