That's been my understanding of it for many years, and I've heard
others say likewise.
If a server wanted to say "Please don't POST to this URI", they could
just respond with a 405 Method Not Allowed. 4xx responses have a
"don't do that again" semantic anyway...
Cheers,
On 2006/10/15, at 2:48 AM, Henrik Nordstrom wrote:
lör 2006-10-14 klockan 10:03 -0700 skrev Mark Nottingham:
Note that when POST is cached, it's future GETs that will get the
cached response, not POSTs (which will be forwarded to the origin).
Are you sure this is what the RFC means? Doesn't make much sense given
the function of POST. I don't see how a GET can be considered
equivalent
to a POST.
I thougt the statement allowing caching of POST responses under
specific
conditions is mainly to allow caching of permanent error responses
such
as 404 or 410 allowing the server to say "please don't POST to this
URI
again..".
Regards
Henrik
--
Mark Nottingham
mnot@xxxxxxxxxxxxx
