| Summary: | ktorrent always use keep-alive in web-interface | ||
|---|---|---|---|
| Product: | [Applications] ktorrent | Reporter: | tuupic <tuupic> |
| Component: | general | Assignee: | Joris Guisson <joris.guisson> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
tuupic
2010-02-01 17:54:29 UTC
First of all the HTTP server does not support HEAD. Second how does using keep-alive prevents the webinterface from being proxied ? It was just example, that ktorrent use keep-alive by default. Nginx use only HTTP/1.0 without keep-alive for backend. In HTTP/1.0 keep-alive disabled by default and server(ktorrent) must not answer HTTP/1.1 answer on HTTP/1.0 request. SVN commit 1100501 by guisson: Fix handling of keep-alive in webinterface plugin BUG: 225167 M +1 -0 ChangeLog M +52 -3 plugins/webinterface/httpclienthandler.cpp M +3 -2 plugins/webinterface/httpclienthandler.h M +5 -3 plugins/webinterface/httpresponseheader.cpp M +4 -1 plugins/webinterface/httpresponseheader.h M +10 -11 plugins/webinterface/httpserver.cpp M +1 -1 plugins/webinterface/httpserver.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1100501 |