RE: WhenToUseGet-7 comments

> > *mark*, not *make*. i.e. a POST operation might _be_
> > safe (e.g. markup validator with file upload), but in the current
> > HTTP protocol, the client has no way to know that it's
> > safe. It has to assume that POST operations are unsafe.
> >
> 
> Yup.  Unless there's a marker of some kind.

> How would that be done in the current protocol?

Been there. Done that.

RFC 2310 The Safe Response Header Field. K. Holtman. April 1998.
(Status: EXPERIMENTAL)

http://www.ietf.org/rfc/rfc2310.txt

This was lengthily discussed, but not accepted as
standards track because there was no consensus among
the implementors of HTTP that it would ever be used
or useful.

Larry
-- 
http://larry.masinter.net

Received on Friday, 19 September 2003 02:45:35 UTC