Cap-go/capacitor-inappbrowser

feat: Persistent Headers

Opened this issue · 0 comments

Current problem

The InAppBrowser plugin is a powerful tool for opening WebViews and offers the ability to inject headers during the initial request. However, during navigation within the WebView, the custom headers (e.g., Authentication) are lost in subsequent requests. This creates challenges for use cases where a consistent header (e.g., for authentication or tracking) is required throughout the user’s session.

Preferred solution

Enable the ability to inject custom headers for the request and all subsequent requests for the same host the WebView. This could be achieved by:
1. Intercepting all outgoing requests from the WebView.
2. Automatically appending the custom headers to each request.

Alternative options

No response

Additional context

No response

Before submitting

Fastest way to get this feature added