HTTP/2 requests are improperly reconstructed

[aph3rson]

Hey folks,

I'm seeing some examples in an API where, when HTTP/2 requests are enabled (and AWS Signer is signing the request), the request is malformed and rejected by the API server.

Some things I've noted:

• Disabling signing in AWS Signer on an HTTP/2 request allows the request to go through
• Enabling signing in AWS Signer for the same request causes the request to be unparsable at the API server (an ALB)
• Disabling HTTP/2 support (either in project settings, or in the Inspector window in Repeater) causes the request to go through (again).

AWS Signer and Logger++ seem to be mis-interacting as well, as I'm unable to view the response data for HTTP/2 requests in Logger++ after AWS Signer signs the request.

Any ideas?