Ludovic Courtès <l...@gnu.org> writes: >> On IRC there was the idea to provide “url-fetch/wget” which would be >> less strict compared to the default Guile HTTP client. > > We could do that, but I would prefer fixing and/or monkey-patching the > date header check in Guile. > > In this case, if the problem is date header validation, it seems that we > could monkey-patch the ‘parse-rfc-822-date’ procedure of (web http) to > do the right thing.
Actually, in this case it’s (again) the ETag header. ~~~~~~~~~~~~~~~~~~~ rekado in guix: wget -S --spider http://icedtea.classpath.org/hg/icedtea/archive/icedtea-3.0.0pre09.tar.gz [...] --2016-03-26 10:02:08-- http://icedtea.wildebeest.org/hg/icedtea/archive/icedtea-3.0.0pre09.tar.gz Resolving icedtea.wildebeest.org (icedtea.wildebeest.org)... 80.127.118.211 Connecting to icedtea.wildebeest.org (icedtea.wildebeest.org)|80.127.118.211|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 200 Script output follows Date: Sat, 26 Mar 2016 09:02:18 GMT Server: Apache/2.4.10 (Debian) Content-Disposition: attachment; filename=icedtea-icedtea-3.0.0pre09.tar.gz ETag: 1458585778.0 Keep-Alive: timeout=5, max=100 Connection: Keep-Alive Content-Type: application/x-gzip Length: unspecified [application/x-gzip] Remote file exists. ~~~~~~~~~~~~~~~~~~~ Is this something we want the Guile HTTP client to be more tolerant about? ~~ Ricardo
