<div dir="ltr"><div>This has landed on master, please give it a go if you want to try it out.</div><div><br></div><div>Regards,</div><div>Marc</div><div class="gmail_extra"><br><div class="gmail_quote">On 13 January 2017 at 17:33, Marc Savy <span dir="ltr"><<a href="mailto:marc.savy@redhat.com" target="_blank">marc.savy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Based upon a community request, I'm making a small patch that ensures the Content-Length header is left intact when no data policies are in the pipeline (instead of using chunked encoding). This is handy if you want the client to know how far downloaded their file is, for instance.</div><div><br></div><div><b>Let me know if this might have any adverse impact upon you.</b></div><div><br></div><div>Example:</div><div><br></div><div>CORS <-> Rate Limiting - Content-Length set.</div><div>CORS <-> [ URL Rewriting ] - Transfer-Encoding: chunked; *no* Content-Length set.</div><div><br></div><div>We don't set Content-Length in cases when body mutation may occur because it would require buffering to determine the final size before transmission - which is something we avoid for performance reasons.</div><div><br></div><div>Regards,</div><div>Marc</div></div>
</blockquote></div><br></div></div>