[htdig3-dev] HTTP/1.0 vs HTTP/1.1 and date class

Gabriele Bartolini (g.bartol@comune.prato.it)
Fri, 16 Apr 1999 12:48:00 +0200

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Gabriele Bartolini: "[htdig3-dev] ETag response-header"
• Previous message: Budd, S.: "RE: [htdig3-dev] Use of & as CGI variable separator vs. HTML 4.0"
• Next in thread: Geoff Hutchison: "Re: [htdig3-dev] HTTP/1.0 vs HTTP/1.1 and date class"

Ciao folks,

I've noticed that Ht://Dig uses HTTP/1.0 to retrieve documents. What
happens if we use HTTP/1.1 instead of it, by any chance? There would be any
compatibility problems with servers that don't support HTTP/1.1? And
overall, are there any meaningful (for htdig, obviusly) differences between
them?

The second question is: why doesn't Ht://Dig uses a date class to store and
manage in a Object Oriented way the date information?

-Gabriele

-------------------------------------------------

Gabriele Bartolini
U.O. Rete Civica - Comune di Prato
Prato - Italia - Europa

e-mail: g.bartol@comune.prato.it
http://www.po-net.prato.it

-------------------------------------------------
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
htdig3-dev@htdig.org containing the single word "unsubscribe" in
the SUBJECT of the message.

• Next message: Gabriele Bartolini: "[htdig3-dev] ETag response-header"
• Previous message: Budd, S.: "RE: [htdig3-dev] Use of & as CGI variable separator vs. HTML 4.0"
• Next in thread: Geoff Hutchison: "Re: [htdig3-dev] HTTP/1.0 vs HTTP/1.1 and date class"

This archive was generated by hypermail 2.0b3 on Fri Apr 16 1999 - 03:57:23 PDT