Subject:
|
Re: Brickshelf suggestions (was: problems?)
|
Newsgroups:
|
lugnet.publish
|
Date:
|
Fri, 28 Jun 2002 15:37:19 GMT
|
Viewed:
|
3338 times
|
| |
|
|
In lugnet.publish, Dan Boger writes:
>
> unless there's an explicit header saying the cgi has expired
Yes.
A GET CGI is supposed to give the same output when it's
> parameters are the same, so browsers are supposed to cache it's output:
>
> from rfc 2068:
>
> In particular, the convention has been established that the GET and
> HEAD methods should never have the significance of taking an action
> other than retrieval. These methods should be considered "safe." This
> allows user agents to represent other methods, such as POST, PUT and
> DELETE, in a special way, so that the user is made aware of the fact
> that a possibly unsafe action is being requested.
Where does it say that a GET request always returns the same content?
a GET for a dynamic page is no different than a GET for a "static" page
that might change at some point. Where the Expires header is set it should
always be obeyed. Now, I am setting "Expires: 0" instead of a properly
formatted date string, so Mozilla may be ignoring it, where IE and NS
know what that means.
> and
>
> Methods may also have the property of "idempotence" in that (aside
> from error or expiration issues) the side-effects of N > 0 identical
> requests is the same as for a single request. The methods GET, HEAD,
> PUT and DELETE share this property.
>
> not saying that this is strictly followed, but this is how it's supposed
> to work :)
>
> Dan
|
|
Message has 1 Reply:
 | | Re: Brickshelf suggestions (was: problems?)
|
| (...) wait - am I completely confused here? I thought we wanted the cgi output to NOT expire? so that "back" will show you the same page? (...) hmmm... : 13.9 Side Effects of GET and HEAD Unless the origin server explicitly prohibits the caching of (...) (23 years ago, 28-Jun-02, to lugnet.publish)
|
Message is in Reply To:
| | Re: Brickshelf suggestions (was: problems?)
|
| (...) unless there's an explicit header saying the cgi has expired (which i didn't check), I say mozilla is doing the Right Thing, while IE and NS don't. A GET CGI is supposed to give the same output when it's parameters are the same, so browsers (...) (23 years ago, 28-Jun-02, to lugnet.publish)
|
85 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
