May not have been that easy after all. Will investigate further..

I tried to re-write the entire proxying mechanism by re-using more from our handler chain, but there still seem to be several issues related to headers and streaming data, which I think is a result of the proxy mechanism on both sides doing too many things to the request.

I need to sit down with@whummer to better understand what the components should be doing exactly before moving forward, because I'm shotgun debugging at this point.

Thanks for digging into this@thrau and getting the extension upgraded to the new gateway logic! 🙌 Happy to do some pairing on this - or maybe I'll find some time this weekend to dig into it a bit.. Let's compare notes soon!

@thrau Sorry for the delay, finally got a chance to look into this. Great job on the refactoring and removing the use ofhttp2_server! 🚀 Pushed a small change to dropTransfer-Encoding headers from the proxied response, see:https://github.com/localstack/localstack-extensions/pull/62/files#diff-ee721dbb335a260769d713b880c29dc772e825e268aedea2a0b3d67fd7f99bc3R46-R47

Was running some quick tests locally, seems to be working. 🎉 At least for S3 requests - these buckets are proxied from a real AWS account:

$ awslocal s3 ls2024-06-20 22:25:33 ls-test-whummer-1232024-06-20 22:51:04 test-bucket-a8c53ada

SQS tests still seem to be failing in the CI pipeline, we can look into those next.. 👀