Dave Carlson wrote:
>
> It looks like the problem is with a *old* last-modified date returned from
> the xmlhack.com server. I sent a HEAD method to www.xmlhack.com and to
> w.moreover.com with the log results appended below.
>
> xmlhack.com returns a last-modified date of Nov 1, 1999
>
> moreover.com looks OK with a last-modified date of Jul 7, 2000
>
> www.xmlhack.com
> HEAD / HTTP/1.0 /rss.php
>
> HTTP/1.1 200 OK
> Date: Sun, 09 Jul 2000 17:26:39 GMT
> Server: Apache/1.2.6 FrontPage/3.0.4
> Last-Modified: Mon, 01 Nov 1999 08:54:52 GMT
ug... NOT good.
I couldn't figure out where they were getting this date from. Then I
realized that it was probably the OS version of the last modified
version of their .php file. :(
I just assumed most dynamic content engines would use a current time
impl by default. The Servlet spec says that if you don't provide your
own impl getLastModification() it just returns the current time. :(
Yes. We will have to use the OCS refresh mechanism.
I will put this in a 1.2b2...
There are a bunch of bugs/features I plan on cranking out next week
(when my life settles).
<snip>
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN Microsystems: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
