reverseproxy: Don't buffer chunked requests (fix #5366)#5367
Conversation
|
I could remove |
francislavoie
left a comment
There was a problem hiding this comment.
Seems good to me.
I think we can just deleted the chunked encoding code. If users who that fix helped find that they need buffering, they can enable it for themselves (and now, set limits).
|
@mholt |
|
@u5surf No worries, thank you for checking it out! And thank you for the original patch. The mistake was my oversight. Hope you'll contribute again. |
Co-authored-by: Y.Horie <[email protected]>
Co-authored-by: Y.Horie <[email protected]>
Co-authored-by: Y.Horie <[email protected]>
|
@u5surf Ah wow, thank you for your review -- I had a lot going on yesterday and looks like I got distracted during a search-replace and mixed them up 🙈 Thank you for catching those errors! I've pushed what I hope is the final change for this patch. |
Mostly reverts 845bc4d (#5289) -- that was my bad, totally an oversight on my part of the code review.
Adds warning for unsafe config. The
buffer_requestsandbuffer_responsesconfig params, together with a separatemax_buffer_sizeparameter, were not safely designed: very prone to configuring unbounded buffers. I'm not sure why I ever thought that was fine.Deprecates unsafe properties in favor of simpler, safer designed ones.
We'll need a better fix for #5236 -- even if it's the same kind of fix (buffering, and resetting the Content-Length) as long as it's opt-in this time.
/cc @u5surf What do you think?
I think this patch merits a quick release of v2.6.4.