The old use of Eventlet's posthook process meant that responses that
forgot to include content-length or transfer-encoding headers would
get one tacked on, if Eventlet could guess what was probably meant. I
added a bit of that logic into proxy-logging now as we saw some
errors resulting from this.
Reviewed: https:/ /review. openstack. org/8458 github. com/openstack/ swift/commit/ 8b778c706af47f4 804c9c4d7217618 5142e6127c
Committed: http://
Submitter: Jenkins
Branch: master
commit 8b778c706af47f4 804c9c4d7217618 5142e6127c
Author: gholt <email address hidden>
Date: Wed Jun 13 00:40:44 2012 +0000
Make proxy-logging more like eventlet.posthook
The old use of Eventlet's posthook process meant that responses that
forgot to include content-length or transfer-encoding headers would
get one tacked on, if Eventlet could guess what was probably meant. I
added a bit of that logic into proxy-logging now as we saw some
errors resulting from this.
Fixes Bug #1012714
Change-Id: I671453eaf3704e ab814ff12c4625b a7d749cc7ed