-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.4.0 Beta2
-
None
-
All
-
55d10201dc7a47b239825548e053c1fb0de61115
-
Foundation Sprint 62, Foundation Sprint 63, Foundation Sprint 64, Foundation Sprint 65, Foundation Sprint 66, Foundation Sprint 67, Foundation Sprint 68, Foundation Sprint 69, Foundation Sprint 70
QAbstractHttpServer is allocating a single QHttpServerRequest object per connection. This works fine as long as the server does not start reading next request from until the current one is done processing. This is probably broken when handlers returning QFuture are used and the client does request pipelining.
If reproducing the bug using Qt, note that QNetworkManager may create up to 6 connections before attempting pipelining.
- is required for
-
QTBUG-75081
Improve the implementation of concurrent processing in the Qt HTTP server and document it
-
- Closed
-
| For Gerrit Dashboard: QTBUG-105202 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 424638,2 | WIP: Pipelined QFuture requests handling | dev | qt/qthttpserver | Status: ABANDONED | -2 | 0 |
| 425116,13 | WIP: Add connection tracking | dev | qt/qthttpserver | Status: ABANDONED | -2 | 0 |
| 431756,11 | Add connection tracking | dev | qt/qthttpserver | Status: MERGED | +2 | 0 |
| 439942,5 | Remove QHttpServerResponse::write() and add QHttpServerResponder::writeResponse() | dev | qt/qthttpserver | Status: MERGED | +2 | 0 |