https://issues.apache.org/bugzilla/show_bug.cgi?id=52547
Bug #: 52547
Summary: incorrect byeswritten log after completed async
request under http1.0
Product: Tomcat 7
Version: 7.0.25
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Connectors
AssignedTo: dev@tomcat.apache.org
ReportedBy: david...@msn.com
Classification: Unclassified
AbstractHttp11Processor does not call nextRequest() if the socket will be
closed because keepAlive=false (i.e. http/1.0).
See line 1539 in
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_25/java/org/apache/coyote/http11/AbstractHttp11Processor.java
Presumably the recycle() caused by the socket close is expected to subsume the
behaviour of nextRequest()
But in AbstractOutputBuffer recycle() does not have byteCount = 0, whereas
nextRequest() does.
See lines 260, 280 in
http://svn.apache.org/repos/asf/tomcat/tc7.0.x/tags/TOMCAT_7_0_25/java/org/apache/coyote/http11/AbstractOutputBuffer.java
The result is that the bytesWritten log of the following request will be
incorrectly increased by the size of the async http/1.0 request
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
