Are you serious? I don't generate request headers. The browser does. And they do so identically whether the HTTP method is PUT or POST and whether it's an XMLHttpRequest or not. And I suspect that they've been doing so pretty much since Marc Andreesen was still in Champaign-Urbana and Mosaic was still an unrealized dream.
I'm certain you're not suggesting that browsers be forced to insert a name before the parameter string in every POST request. Tomcat would instantly cease to be a viable option for pretty much everyone. So why are you harping on PUT? In fact, what is it with this list? Is this the PUT Haters Club? Why do I have to defend my decision to use PUT requests? Why do I have to keep explaining an RFC that should be near and dear to the hearts of anyone who works with web servers? What does *any* of this have to do with a simple post to the list explaining that parameters passed with a PUT request seem to be stripped out by Tomcat (though not by Jetty), and asking if this was a bug or intended behavior? It's a mystery to me. Chas. > On Fri, Feb 5, 2010 at 4:13 PM, <c...@munat.com> wrote: > >> PUT /json/members/1b35d32f-714d-4393-b8c2-b4805e0c7a13 HTTP/1.1 >> Host: localhost:12344 >> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; >> rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 >> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 >> Accept-Language: en-us,en;q=0.5 >> Accept-Encoding: gzip,deflate >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 >> Keep-Alive: 300 >> Connection: keep-alive >> X-Requested-With: XMLHttpRequest >> Content-Type: application/x-www-form-urlencoded; charset=UTF-8 >> Referer: http://localhost:12344/ >> Content-Length: 297 >> Cookie: JSESSIONID=dexcmg3b1r45 >> emailAddress=bozo%40clown.com&title=Head%20Clown&nameGiven=Bozo&namesMiddle=The&nameFamily=Clown&namePreferred=Bozo&gender=Male&password=&passwordConfirm=&id=1b35d32f-714d-4393-b8c2-b4805e0c7a13&facebookName=bozo.the.clown&twitterName=i.am.bozo&flickrName=bozos.circus&linkedinName=mr.clown.to.you > > (RFC 2616) > 4.2 Message Headers > > HTTP header fields, which include general-header (section 4.5), > request-header (section 5.3), response-header (section 6.2), and > entity-header (section 7.1) fields, follow the same generic format > as that given in Section 3.1 of RFC 822 [9]. Each header field > consists of a name followed by a colon (":") and the field value. > > Have you tried this using such a header format? e.g. > > Bozo-Fields: > emailAddress=bozo%40clown.com&title=Head%20Clown&nameGiven=Bozo&yaddayaddayadda > > Just wonderin' ... > -- > Hassan Schroeder ------------------------ hassan.schroe...@gmail.com > twitter: @hassan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
