Hi, If I download a sqlite, here is the first bit of a wget transcript:
$ wget -S https://sqlite.org/2016/sqlite-autoconf-3140100.tar.gz --2016-08-30 23:15:34-- https://sqlite.org/2016/sqlite-autoconf-3140100.tar.gz Resolving sqlite.org (sqlite.org)... 2600:3c00::f03c:91ff:fe96:b959, 67.18.92.124 Connecting to sqlite.org (sqlite.org)|2600:3c00::f03c:91ff:fe96:b959|:443... failed: Connection refused. Connecting to sqlite.org (sqlite.org)|67.18.92.124|:443... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Connection: keep-alive Date: Tue, 30 Aug 2016 21:15:35 +0000 Last-Modified: Sat, 27 Aug 2016 23:54:32 +0000 Content-type: application/x-gzip Content-length: 2473610 Length: 2473610 (2.4M) [application/x-gzip] Saving to: ‘sqlite-autoconf-3140100.tar.gz’ However these Date and Last-Modified headers are invalid according to RFC 2616. Note the extra spaces, which are not allowed. See section 3.3.1 of the RFC. I noticed this by maintaining Guile, a language implementation that has its own HTTP client. We sometimes have these problems, and sometimes work around them and sometimes get people with custom web servers to be more compliant. In this case as it is only for sqlite and fossil I assume you might be willing to comply with the RFC. What do you think? Regards, Andy _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users