Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 324260

Summary:	Continuation compatibility broken for use with jetty-6
Product:	[RT] Jetty	Reporter:	Jan Bartel <janb>
Component:	server	Assignee:	Greg Wilkins <gregw>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	jetty-inbox
Version:	7.1.5
Target Milestone:	7.1.x
Hardware:	All
OS:	All
Whiteboard:

Description Jan Bartel

2010-09-01 20:32:08 EDT

The jetty-continuation ContinuationFilter does not appear to be working correctly when deployed on jetty-6.

The scenario:

Deploy the jetty-7 ProxyServlet and configure the ContinuationFilter on jetty-6. Requests to the ProxyServlet hit the proxied server and the reply comes back just fine, yet the ProxyServlet always returns 504 Gateway Timeout to the requestor.

The only place this happens in the ProxyServlet code is when a Continuation is replayed and we check continuation.isInitial(). In fact, as the proxy request completes ok, and calls continuation.complete() the Continuation should not be replayed into the servlet.

Comment 1 Greg Wilkins

2010-09-01 21:41:05 EDT

The jetty-6 continuation handling was still allowing a completed request to be passed to the servlet.

The fix was to make enter() return !_complete

r2236