Bug 55819 - Closing connection behaviour
Summary: Closing connection behaviour
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.2.3
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2013-11-27 15:23 UTC by Moltes12
Modified: 2018-11-07 21:08 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moltes12 2013-11-27 15:23:37 UTC
Hello.

I'm running Apache 2.2.3 as reverse proxy.
There are multiple virtual hosts running SSL.

I receive some requests with the "Connection: close" header set.
The connection is done under http version 1.0.
When my server is returning the response, the response is in http version 1.0, with the header "Connection: close" set.

My client is claiming me that his application connecting my server is waiting my server to close the connection. At the end, his application is very slow because it spend a lot of time to wait my server to close the connection.
If a do network capture using wireshark, I can see that the server sends FIN tcp flag after 10 or 15 seconds the response.

Is this a normal behaviour ?
How can I set up Apache to close the connection just after the response is given ?

Thanks.
Comment 1 Eric Covener 2013-11-27 15:47:45 UTC
You'll need to show some kind of packet capture. If you can recreate on an idle system, get a backtrace with e.g. gdb a few times in that 10-15 second window.

http://httpd.apache.org/dev/debugging.html
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:39 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.