Tim Burke

FWIW, I think the failure had to do with `CallbackEnablingBody` always being a False-y value, meaning that when we'd prepare the request, we'd pass a `None` body to requests. See...

Anything else I should do to help move this forward?

It's been a couple years now... Anything I can do to help move this forward?

I was hitting the same issue, but after upgrading the server to Frodo (12.2), it seems to be working properly. From the store page: This is a release update for...

Seems to have been addressed back in January.

FWIW, this also [impacts `wsgiref`](https://github.com/python/cpython/blob/v3.11.0/Lib/wsgiref/simple_server.py#L71), which seems not-great considering how it's supposed to be a reference implementation. This example has the same bad behavior as above, except with a different...

Yeah, unfortunately patching out `eventlet.websocket.DEFAULT_MAX_FRAME_LENGTH` won't do much since the 8MB value gets baked into the signature of `WebSocketWSGI` and `RFC6455WebSocket`. I remember bringing up the idea of how an...

I was looking at all this again recently, and rediscovered https://github.com/eventlet/eventlet/issues/546 (i.e., `_green_existing_locks` doesn't work on py3 _anyway_) I _think_ py310 finally got the existing RLocks to show up in...

I'm not entirely sure whether we ought to be the ones doing this. It's not _so_ bad doing it from the application, especially if it's already providing its own `HttpProtocol`...

Hmm. Well, * The issue [wasn't as easy to fix in application code as I'd originally hoped](https://github.com/openstack/swift/commit/bf9346d88de2aeb06da3b2cde62ffa6200936367), and * [poses a security concern](https://bugs.launchpad.net/swift/+bug/1840507) because of the request-smuggling opportunities. :disappointed: I'm...