From: Michael Leuchtenburg Date: 00:05 on 14 Jul 2006 Subject: wget's double-slash URL munging I have this little Python script that proxies last.fm. It likes to take, as input, a lastfm URL in its own URL. This leads to URLs like: http://localhost:1881/lastfm://artist/Mogwai/similarartists This is all well and good - in a sane program. Try passing that to wget, though, and it will instead request: http://localhost:1881/lastfm:/artist/Mogwai/similarartists Note the lack of slash. It also totally neglects to mention this, claiming to be requesting exactly what I told it to. It lies. lastfmproxy, being a complete hack, chokes on this. Now, I could make it stop being a hack, but I didn't write it and damnit, I shouldn't have to. wget should just send the damn URL as I told it to. And, failing that, it should *tell me that it's changing the URL*. CLEARLY I must want it to "correct" thing behind my back without so much as a "by your leave"! After all, wget is much smarter than any user could possibly be. Perhaps this meets with some standard for URLs. That's all well and good, but it should *tell me* and *give me an option to tell it to fuck off and let me bugger the standards in peace*.
Generated at 10:26 on 16 Apr 2008 by mariachi