Comment 2 for bug 1483997

Yes, I can reproduce this, and yes, I get a pair of stack traces in my logs when I do. Also of note: the client receives the normal GET response; they can't tell that anything broke.

However, those stack traces don't contain any references to Swift code. Everything is in eventlet.wsgi or Python stdlib; there's not a single frame that refers to Swift code, so it seems highly unlikely that Swift can do anything about it.

The only improvement I can see right now is that Swift shouldn't pass Transfer-Encoding to the object server on object GET since it's not going to send a body on the GET request. That'd take it from two stack traces to one.

Also, if I actually *send* a GET body, then the proxy doesn't log any stack trace. Only the object server does.