Skip to content

Document implementation restrictions when intercepting web requests #3096

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 18, 2025
Merged

Document implementation restrictions when intercepting web requests #3096

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/user-interface/controls/hybridwebview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1024,4 +1024,19 @@ Common patterns include:
- Returning local files or in-memory content for offline or testing scenarios.
- Redirecting to a different URI by returning a 3xx status code with an appropriate `Location` header.

### Implementation Restrictions

* **Android**
* Android does not directly allow "intercept-and-continue" for requests. The implementation is to rather notify you that a request is about to happen and you can either replace the whole request or do nothing and let the webview do it.
* Android does not support custom schemes.
* **iOS/Mac Catalyst**
* iOS and Mac Catalyst do not allow interception of `http` and `https` requests.

| Platform | Intercept HTTPS | Intercept Custom Schemes | Request Modification |
|---------------|------------------|---------------------------|----------------------|
| Android | ✅ | ❌ | ❌ |
| iOS | ❌ | ✅ | ❌ |
| Mac Catalyst | ❌ | ✅ | ❌ |
| Windows | ✅ | ✅ | ✅ |

::: moniker-end