feat(http): add transport extension hooks - #3538
Open
patlux wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
tauri-plugin-httpcurrently creates an internalreqwest::ClientBuilderfor every request without exposing a native customization point. Applications that need transport-level policies or custom TLS backends must therefore replace the fetch-compatible plugin surface with custom commands.This change adds trusted native transport extensions while preserving the existing JavaScript API and default
init()behavior.Design
tauri_plugin_http::Builder<R>registers extensions in deterministic order.HttpTransportExtension<R>exposes fallible setup, request validation, finalreqwest::ClientBuilderconfiguration, and transport-error mapping.RequestContextprovides owned request metadata without exposing request bodies.ExtensionErrorforwards extension-owned structured JSON through IPC while existing plugin errors remain strings.This provides a general foundation for native transport concerns such as custom TLS verification, mTLS, request policy enforcement, and transport diagnostics. SPKI pinning from #3414 can be implemented as a separate extension on top of this API.
Follow-up implementation: #3539.