Geoff Hutchison (firstname.lastname@example.org)
Tue, 02 Feb 1999 21:13:27 -0400
> Header line: HTTP/1.1 200 OK
> Header line: Server: Microsoft-IIS/4.0
> Header line: Date: Wed, 03 Feb 1999 01:12:44 GMT
> Header line: Content-Type: text/html
> Header line: Cache-Control: no-cache="set-cookie,set-cookie2"
> Header line: Last-Modified: 27 Jan 1999 01:12:44 GMT
This last line is invalid. Last-modified headers should have a format like:
Header line: Last-Modified: Mon, 2 Feb 1999 01:12:44 GMT
So you say "I don't care if it's invalid, ht://Dig should be able to keep
going." Fair enough. But I'm beginning to worry about the complexity of that
section of code if people keep finding non-compliant servers. There's a
reason for RFCs...
What should we do, decide that we'll give the current time to documents from
servers that return poorly-formatted dates? That doesn't sound like a good
solution to me.
Williams Students Online
To unsubscribe from the htdig mailing list, send a message to
email@example.com containing the single word "unsubscribe" in
the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Wed Feb 10 1999 - 17:09:05 PST