Repository navigation
Commit a8106d9
reqwest: re-apply 0.13 bump at 0.13.4 with explicit TLS backend pin
Re-application of MaterializeInc#36215 (reverted in MaterializeInc#36241 for flaky Kafka auth
schema-registry TLS tests) with three changes:
- reqwest 0.13.4 instead of 0.13.2. Upstream has since fixed several
bugs in the TLS config layer, notably PEM parsing of CRL values and
native-tls ALPN/TLS 1.3 handling. sentry 0.47 already ships reqwest
0.13.3 in our tree, so 0.13 itself is not new here.
- ccsr pins its client to tls_backend_native(). reqwest 0.13 defaults
to rustls whenever transitive deps compile the rustls backend in, and
ccsr's certificates and identities are prepared for native-tls. The
April flake surfaced OpenSSL PEM errors at connect time on exactly
this client, consistent with TLS backend/verifier drift.
- The Azure transport client comes from the reqwest_0_12 alias, keeping
the BlobKnobs timeout plumbing on both the emulator and production
paths. azure_core 0.21 implements HttpClient only for reqwest 0.12.
The alias also covers iceberg's RequestAuthenticator, which gained a
second impl (Sigv4Authenticator) since April.
Co-Authored-By: Claude Fable 5 <[email protected]>1 parent b8f14cb commit a8106d9
3 files changed
Lines changed: 64 additions & 42 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
104 | 104 | | |
105 | 105 | | |
106 | 106 | | |
107 | | - | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
| 111 | + | |
108 | 112 | | |
109 | 113 | | |
110 | 114 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
61 | 61 | | |
62 | 62 | | |
63 | 63 | | |
64 | | - | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
65 | 67 | | |
66 | 68 | | |
67 | 69 | | |
| |||
0 commit comments