Bug 44087 - tomcat-native-1.1.10 duplicate requests on tcp connection
Summary: tomcat-native-1.1.10 duplicate requests on tcp connection
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Native:Integration (show other bugs)
Version: Unknown
Hardware: Other Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-17 14:12 UTC by admin
Modified: 2007-12-23 12:52 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description admin 2007-12-17 14:12:58 UTC 
Using jboss 4.2.1 (based on tomcat 5.5), with tomcat-native-1.1.10 installed, 
and SSL enabled.  Connecting to port 8443 (https port) using netcat and then 
disconnecting without sending any data will cause tomcat to handle a duplicate 
copy of one of the recent requests.  For example, a client at 10.0.0.1 is 
making HTTP GET requests for https://someserver:8443/someurl?foo=1, with foo 
being incremented on each request.  If you connect to the https port from 
10.0.0.2 and then disconnect without sending any data, the access log will show 
10.0.0.2 issuing a request for someurl?foo=some_recent_number.
Comment 1 Mark Thomas 2007-12-23 12:52:24 UTC 
This has been fixed in svn and will be included in native 1.1.12 onwards.