Fix signing when Hyper ALPN negotiates to h2 (#674)
The endpoint middleware was adding a host header to the request, and this worked when using HTTP/1.1. However, when the connection gets upgraded to h2, this results in the remote service expecting the canonical request to have two `host` headers. This change moves the addition of the host header into the signing code, and lets hyper take charge of the host header. * Update changelog * Remove `transcribestreaming` exclusion from full SDK build * Fix failing tests * CR feedback
Loading
Please register or sign in to comment