tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier>
Subject Re: [Fwd: Re: Parameters disappear from PUTs]
Date Fri, 05 Feb 2010 21:38:15 GMT 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.
Just to situate things, I am not one of the Tomcat developers, merely a 
user. So whatever I say about Tomcat below is relatively speculative and 
under my own responsibility only.
Furthermore, my knowledge of REST is very scarce, but I gather that it 
is a protocol/architecture (?) implemented, in this case, on top of HTTP.
I am a long-time user of HTTP, so in that respect, if only by virtue of 
repetition, I feel on more solid ground.

Tomcat is a servlet engine, and a HTTP server.  It is not a REST server 
nor client, and does not claim to be.

This does not mean that you are wrong in your main contention; but means 
that if Tomcat does things right with respect to the Java Servlet Spec 
and the HTTP protocol, then Tomcat fulfills its contract, and whatever 
would be missing to also make it be a REST server would not be a bug, 
and merely an inconvenience.  And if so, you /might/ be able to persuade 
the developers of lifting the inconvenience, or better yet, submit a 
patch for ditto.

In your previous posts, you have not been very clear about what you 
meant by "parameters", and later you have mentioned HTTP headers instead.
If Tomcat was indeed "stripping" HTTP headers from a PUT request (iow 
making it impossible for a servlet to retrieve them), then I would tend 
to agree that this is a bug, because I see nothing in the HTTP spec that 
indicates that a PUT should not contain HTTP headers (at the contrary even).

But is that really what happens ?
Christopher asked you previously to confirm that point, but you didn't 
Or are you talking about parameters sent as part of the request line, 
like in a query string ?
Can you give us an example of how you are sending these "parameters", 
and how exactly you (attempt to) retrieve them in the web application ?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message