- From: David W. Morris <dwm@shell.portal.com>
- Date: Fri, 5 Jan 1996 13:13:19 -0800 (PST)
- To: HTTP Caching Subgroup <http-caching@pa.dec.com>
On Fri, 5 Jan 1996, Shel Kaphan wrote: > David W. Morris writes: > > I must be truly dense ... why wouldn't the sine server be implemented > > with GET? > > > > It's mostly a thought experiment. Due primarily to URL length > limitations, POST is often used where GET would semantically be sufficient. > > > > URL length is a practical consideration that muddies this issue. Well, it doesn't seem like a major extension to the GET method to allow for an entity body from the HTTP documents perspective. Use the ENCTYPE attribute of the FORM element to tell the UA to use urlencoding in the entity body for GET rather than the URL. This improves privacy as well in that the URL no longer would contain sensitive data. From a CGI application perspective it is trivial to extend the input parsing to combine the URL and entity data. My deployed applications already do it because I have observed early UAs which either ignored the method or handled POST like GET. A minor UA change. No requirement for a new method. Dave
Received on Friday, 5 January 1996 21:28:50 UTC