Enable ALPN feature in reqwest
crate
#1318
Merged
+87
−48
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Google AI returns a confusing
HTTP 400
error with messageINVALID_ARGUMENT
if the ALPN negotiation is not supported by the client:This PR enables the
native-tls-alpn
feature for thereqwest
crate which handles the ALPN extension for TLS.Important
Enable ALPN support in
reqwest
to fix HTTP 400 errors from Google AI by updating dependencies and enablingnative-tls-alpn
.native-tls-alpn
feature inreqwest
crate to support ALPN negotiation, resolving HTTP 400 errors from Google AI.reqwest
version to0.12.12
inCargo.toml
andbaml-runtime/Cargo.toml
.bytes
to1.9.0
,hyper-util
to0.1.10
, andopenssl-src
to300.4.1+3.4.0
inCargo.lock
.windows-registry
andtower 0.5.2
dependencies inCargo.lock
.This description was created by for b1b32c0. It will automatically update as commits are pushed.