On 9 February 2010 15:26, Christopher Schultz
wrote:
> I've learned a lot from
> reading and participating in many discussions on this list, and I think
> you probably will, too, if you stick around.
I think many of us have learned a lot. Sometimes it's been technical,
sometimes on how to deal w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chas,
On 2/8/2010 10:24 PM, c...@munat.com wrote:
>> I'm unaware of any uses of PUT that automatically parse the request body
>> on behalf of the user's code. Instead, the user's code is typically
>> expected to handle the entire request body. Apache
Chris,
> I realize that this issue has been essentially solved, but it's probably
> worth it to continue the discussion.
Happy to continue if it's productive.
> I routinely use Firefox and LiveHTTPHeaders: that add-on definitely does
> indicate what is form data for a POST request, but I've neve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chas,
I realize that this issue has been essentially solved, but it's probably
worth it to continue the discussion.
On 2/8/2010 1:51 PM, c...@munat.com wrote:
> That was a response to smoke and hand-waving in another post and certainly
> nothing that
I posted it exactly as it came to me.
> On Saturday 06 February 2010 03:27:23 c...@munat.com wrote:
>> Are you serious?
>
> [...]
>
>> I'm certain you're not suggesting that browsers be forced to insert a
>> name
>> before the parameter string in every POST request.
> [...]
>> What does *any* of t
>> We were discussing RFC 2616. Entity-headers and entity-body are terms
>> directly from the RFC and are defined therein. No, they are not the same
>> as HTTP headers, though they are contained in the HTTP headers:
>
> To-MAY-to, to-MAH-to.
That was a response to smoke and hand-waving in another
On Saturday 06 February 2010 03:27:23 c...@munat.com wrote:
> Are you serious?
[...]
> I'm certain you're not suggesting that browsers be forced to insert a name
> before the parameter string in every POST request.
[...]
> What does *any* of this have to do with a simple
> post to the list explai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chas,
On 2/5/2010 7:13 PM, c...@munat.com wrote:
> We were discussing RFC 2616. Entity-headers and entity-body are terms
> directly from the RFC and are defined therein. No, they are not the same
> as HTTP headers, though they are contained in the HTT
>> In fact, what is it with this list? Is this the PUT Haters Club?
>
> Mainly, it is your attitude. Given you are speaking to a community that
> provides assistance to other members of the community for free, a less
> argumentative tone would go a long way to help.
Ah. I think I see where the pro
On 06/02/2010 02:27, c...@munat.com wrote:
> 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 A
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
s
On Fri, Feb 5, 2010 at 4:13 PM, 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/x
REST -- REpresentational State Transfer -- is an architectural style that
was developed by Roy Fielding with HTTP, but which is independent of HTTP.
No changes need to be made to HTTP to implement REST -- you just need to
implement HTTP correctly. There's a pretty good article on Wikipedia about
RE
> Could you please be clear when you say "entity headers": do you mean
> HTTP headers? I have a Tomcat 6.0.20 install right in front of me that
> definitely does allow the servlet (in my case, a simple JSP that dumps
> requests) to read the HTTP headers. HTTP GET parameters are also
> correctly pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chas,
On 2/5/2010 2:45 PM, c...@munat.com wrote:
> So for Tomcat to unilaterally strip the entity-headers from a PUT request
> while passing only the optional entity-body seems just, well, wrong to me.
Could you please be clear when you say "entity h
c...@munat.com wrote:
...
So for Tomcat to unilaterally strip the entity-headers from a PUT request
while passing only the optional entity-body seems just, well, wrong to me.
For this reason, I'm guessing it's a bug.
Hi.
Just to situate things, I am not one of the Tomcat developers, merely a
> From: c...@munat.com [mailto:c...@munat.com]
> Subject: RE: [Fwd: Re: Parameters disappear from PUTs]
>
> Read the entire section before you comment!
Sorry, I hadn't done that. As I said before, I believe your interpretation is
correct.
- Chuck
THIS COMMUNICATION MAY CON
*quite clear* on the
difference between POST and PUT -- Roy Fielding, et al, did an excellent
job of it.
Can we, finally, let it rest there? (Pun intended.)
Chas.
>> From: c...@munat.com [mailto:c...@munat.com]
>> Subject: Re: [Fwd: Re: Parameters disappear from PUTs]
>>
>>
> From: c...@munat.com [mailto:c...@munat.com]
> Subject: Re: [Fwd: Re: Parameters disappear from PUTs]
>
> RFC 2616 is quite clear on this topic, IMO.
Maybe not.
> The POST method is used "to request that the origin server accept the
> *entity* enclosed in the request
Re PUT, a little research will show that this has been a hot topic for
several years now, at least since Elliotte Rusty Harold's controversial
"Why REST Failed" post in 2006.
RFC 2616 is quite clear on this topic, IMO.
The POST method is used "to request that the origin server accept the
*entity*
Hi.
I'll forward your reply to the list, since apparently you did not.
Let me just point out that I was only trying to help, and I do not
believe that there were any grounds in my reply for the sarcastic tone
used in yours.
In the meantime, I did re-read both sections of the RFC 2616 (9.5 POS
21 matches
Mail list logo
