[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-dev] disable expect continue support
|
It appears tomcat checks container managed authentication (if any) prior
to the 100-Continue, so technically, i guess they are allowing "the
application to decide to accept". But most milton users dont use
container managed authentication so it doesnt actually help.
I've checked milton and it doesnt seem to call getInputStream early. Did
the semantics you describe get implemented in a relatively recent
version of jetty? I think there's still plenty of Jetty6 floating around
in pom.xml's (yes, i'm guilty!) so could that explain these problems?
On 14/02/13 08:35, Simone Bordet wrote:
Hi,
On Wed, Feb 13, 2013 at 8:23 PM, Brad McEvoy <brad@xxxxxxxxxxxxxxxxxxxx> wrote:
BTW: Do you know if other servlet containers implement the same semantics?
No idea.
Or is Jetty just being a bit of a star?
We are anyway :)
I described the same problem to the
tomcat users list and responses appear to confirm that 100-Continue is sent
prior to invoking the servlet.
Well, that would be against the current interpretation of the Http-bis
expert group at IETF.
The main point of 100-Continue is for the application to decide
whether it can accept the request or not, so it would not make much
sense to send it without asking the application :)
Because of the lack of API, Jetty uses getInputStream() as a trigger
for the 100-Continue response, so the application has some degree of
control over _when_ to send the 100-Continue response.
