bug #1496234 is indeed similar, but different scenarios and AFAICT they require separate fixes - the 416 raised by proxy isn't handled in _fix_response place where I fix the etag in patch 293633
bug #1496234 is indeed similar, but different scenarios and AFAICT they require separate fixes - the 416 raised by proxy isn't handled in _fix_response place where I fix the etag in patch 293633