Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Jeff Johnson <jeff@bo...> - 2001-10-12 03:28:15
Here's a new one. What is a REQUEST_METHOD =3D HEAD? Isn't that just =
Traceback (most recent call last):
File "/usr/Webware/Webware/WebKit/Application.py", line 341, in
File "/usr/Webware/Webware/WebKit/Application.py", line 489, in
File "/usr/Webware/Webware/WebKit/Application.py", line 610, in
File "WebKit/Transaction.py", line 93, in respond
File "WebKit/HTTPServlet.py", line 37, in respond
At 11:17 PM 10/11/2001 -0400, Jeff Johnson wrote:
>Here's a new one. What is a REQUEST_METHOD = HEAD? Isn't that just GET
It's like a GET, but it only wants the timestamp in return. Browsers will
ask for a HEAD if they are caching a copy of the document in the hope that
they don't need to get another copy. But I think you said you were setting
the pages to always expire, so no browser should be asking for this.
Obviously one is, so you'd probably want to return the current date and
time, which should be greater than the date and time you vended the
document. Perhaps add some time (like a minute) to guarantee that.
You'll want to double check the HTTP RFC for the definition of HEAD. I'm
speaking from distant memory.
Since WebKit pages are always derived, perhaps Page should default to the
behavior I described. For applications whose pages really do stay the same
over some period of time, the Page author could override this behavior.