Hiho!
Ari Pollak schrieb: > Does this happen for any URL you try? Can you give an example of one > where it fails? It fails with any url. Manish Singh schrieb: > wget -T 300 http://the/url/that/is/failing -O /tmp/testwget > > would help (replace "http://the/url/that/is/failing"; with an actual > example url of course). I didn't know that gimp uses wget for retrieving the url... Actually that gives me an idea. My ~/.wgetrc contains: robots=off server-response=on And thus the output from above command is: [EMAIL PROTECTED]:~$ wget -T 300 http://www.cashab.de/bilder_flaggen/australia.png -O /tmp/testwget --13:46:54-- http://www.cashab.de/bilder_flaggen/australia.png => `/tmp/testwget' Auflösen des Hostnamen »www.cashab.de«.... 80.86.176.132 Verbindungsaufbau zu www.cashab.de[80.86.176.132]:80... verbunden. HTTP Anforderung gesendet, warte auf Antwort... 1 HTTP/1.1 200 OK 2 Date: Thu, 10 Mar 2005 12:45:16 GMT 3 Server: Apache/1.3.31 (Debian GNU/Linux) mod_python/2.7.10 Python/2.3.4 PHP/4.3.9-1 mod_ssl/2.8.20 OpenSSL/0.9.7d mod_perl/1.29 4 Last-Modified: Thu, 03 Feb 2005 01:47:35 GMT 5 ETag: "75408b-1784-420182b7" 6 Accept-Ranges: bytes 7 Content-Length: 6020 8 Keep-Alive: timeout=15, max=100 9 Connection: Keep-Alive 10 Content-Type: image/png 100%[================================================>] 6,020 --.--K/s 13:46:55 (59.01 KB/s) - »/tmp/testwget« gespeichert [6020/6020] I'm not sitting in front of my home machine right now, but I'm fairly certain that the bug will disappear if I remove the server-response parameter. Maybe gimp should add the "-e server-response=off" to its wget call (or improve the output parsing in a way that any options the user might have set in his .wgetrc don't get in the way). I also wonder why they don't look at the return value, which should be 0 in this case. Kind regards and thanks! Friedel -- Friedrich Delgado Friedrichs <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
