| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4457.1 | | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Fri Feb 07 1997 11:04 | 8 |
| > several experiences where I did a date-range search and Altavista "found"
> entries that were much older than this, according to the "last updated"
> massage at the bottom of the page.
AV or any crawler is not getting the document date from the
content of the document itself. It's getting the date from
the HTTP Server (in the HTTP response there is usually a
Date: field. See an HTTP spec for more info).
|
| 4457.2 | | NETCAD::MORRISON | Bob M. LKG2-A/R5 226-7570 | Mon Feb 10 1997 15:16 | 6 |
| > content of the document itself. It's getting the date from
> the HTTP Server (in the HTTP response there is usually a
> Date: field. See an HTTP spec for more info).
I don't have an HTTP spec handy. How is the date field in the HTTP response
set? I assume it is set automatically whenever a certain action is performed.
|
| 4457.3 | Re: How does AltaVista determine dates on date-range searches? | QUABBI::"mogul@actitis.pa.dec.com" | Jeffrey Mogul | Mon Feb 10 1997 21:39 | 18 |
| In article <4457.2-970210-151602@networking.internet_tools>, morrison@netcad.enet.dec.com (Bob M. LKG2-A/R5 226-7570) writes:
|> > content of the document itself. It's getting the date from
|> > the HTTP Server (in the HTTP response there is usually a
|> > Date: field. See an HTTP spec for more info).
|>
|> I don't have an HTTP spec handy. How is the date field in the HTTP response
|> set? I assume it is set automatically whenever a certain action is performed.
The HTTP/1.1 spec says that
The Date general-header field represents the date and time at which the
message was originated
and I believe that the HTTP/1.0 spec says more or less the same thing.
I.e., it has very little to do with when the document (or whatever)
was created, unless it was created on the fly by a script.
-Jeff
[posted by Notes-News gateway]
|
| 4457.4 | | VAXCPU::michaud | Jeff Michaud - ObjectBroker | Fri Feb 21 1997 19:09 | 12 |
| > I don't have an HTTP spec handy. How is the date field in the HTTP response
> set? I assume it is set automatically whenever a certain action is performed.
For non-on-the-fly generated documents, I assume most servers get
the "last modified" or "created" (for those filesystems that have
such a concept) timestamp of the file itself.
For on-the-fly generated documents, I assume either the server
sends a Date: field with the current time, or the script/program
sends it (for script/program interfaces that allow the script/program
to actually append headers after the headers the server has already
sent).
|
| 4457.5 | | CFSCTC::SMITH | Tom Smith MRO1-3/D12 dtn 297-4751 | Fri Feb 21 1997 20:11 | 8 |
| re: .-1
That's my understanding as well. For static documents, that's why clock
skew among the editing client, viewing client, http server, and file
server (if any) can be a factor in strange cache behavior for recently
changed pages.
-Tom
|