-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Coombe, Allan David (DPS) wrote: > OK - now I am confused. > > I found a perl based http proxy (named "http::proxy" funnily enough) > that has filters to change both the request and response headers and > data. I modified the response from the web site to lowercase the urls > in the html (actually I lowercased the whole response) and the data that > wget put on disk was fully lowercased - problem solved - or so I thought. > > However, the case of the files on disk is still mixed - so I assume that > wget is not using the URL it originally requested (harvested from the > HTML?) to create directories and files on disk. So what is it using? A > http header (if so, which one??).
I think you're missing something on your end; I couldn't begin to tell you what. Running with --debug will likely be informative. Wget uses the URL that successfully results in a file download. If the files on disk have mixed case, then it's because it was the result of a mixed-case request from Wget (which, in turn, must have either resulted from an explicit argument, or from HTML content). The only exception to the above is when you explicitly enable - --content-disposition support, in which case Wget will use any filename specified in a Content-Disposition header. Those are virtually never issued, except for CGI-based downloads (and you have to explicitly enable it). - -- Good luck! Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer, and GNU Wget Project Maintainer. http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIXe0Z7M8hyUobTrERAkF5AJ9FOkx5XQJCx9vkTV9xr2zbYzp4jwCffrec zhdtjp59GOwt07YgvtolM8o= =FZ3m -----END PGP SIGNATURE-----
