Bug #12713
closed
civetweb frontend: response is buffered in memory if content length is not explicitly specified
Added by Radoslaw Zarzynski over 8 years ago.
Updated over 4 years ago.
Description
If content length is not explicitly specified by upper layer through a call to RGWMongoose::send_content_length(), civetweb frontend performs extensive buffering in order to properly calculate the size of a content and attach the Content-Length HTTP header. Please take a look on RGWMongoose::write_data() and RGWMongoose::complete_request() methods.
- Status changed from New to In Progress
- Assignee set to Radoslaw Zarzynski
- Status changed from In Progress to Pending Backport
- Priority changed from Normal to High
- Backport set to mimic luminous
- Pull request ID set to 23940
- Copied to Backport #39614: mimic: civetweb frontend: response is buffered in memory if content length is not explicitly specified added
- Copied to Backport #39615: luminous: civetweb frontend: response is buffered in memory if content length is not explicitly specified added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved".
Also available in: Atom
PDF