alphax_web 1.0.0-rc.3

Browser Fetch HTTP transport adapter for AlphaX with streaming, cancellation, and truthful capability reporting.

alphax_web

Run AlphaX through browser Fetch.
Keep the request API while respecting the browser's security and networking controls.

Core API · Native transports · Apache-2.0

At a glance

Browser concern	alphax_web behavior
Transport	Fetch, exposed as an AlphaX transport
Protocol metadata	unknown; Fetch does not expose authoritative H1/H2/H3 information to Dart
Browser controls	CORS, TLS, proxy routing, connection reuse, redirects, and cookie credentials remain browser-owned
AlphaX policies	Authentication, replay-aware retries, in-memory cookies/cache, and generic resilience remain opt-in
Native controls	File paths, SPKI pinning, custom trust anchors, mTLS, explicit proxies, and upload progress are unavailable here

Start here

1. Add alphax and alphax_web.
2. Create WebFetchTransport and an AlphaXClient.
3. Configure CORS and browser credentials on the server/application boundary.
4. Treat protocol metadata as unknown; browser controls remain browser-owned.

alphax_web adds a browser Fetch transport for AlphaX. Use it when the same transport-independent request code must run in a Flutter Web application or a Dart application compiled for the browser.

What you get

• ordinary browser HTTP requests through Fetch;
• AlphaX headers, bodies, response streams, cancellation, timeouts, redirects, and normalized errors;
• browser-managed credential mode through withCredentials; and
• the same middleware layer as native AlphaX transports for authentication, cookies, caching, retries, and resilience policies.

The browser controls TLS, proxies, connection reuse, CORS, and the negotiated HTTP version. Fetch does not expose authoritative H1/H2/H3 metadata to Dart, so the transport reports the protocol as unknown. A concrete protocol requirement fails closed instead of guessing.

Install

flutter pub add alphax alphax_web

First request

import 'package:alphax/alphax.dart';
import 'package:alphax_web/alphax_web.dart';

Future<void> loadHealth() async {
  final client = AlphaXClient(transport: WebFetchTransport());
  try {
    final response = await client.get(Uri.https('example.com', '/health'));
    print('${response.statusCode}: ${await response.readAsString()}');
    print('protocol: ${(await response.completionMetrics).negotiatedProtocol.name}');
  } finally {
    await client.close();
  }
}

The target server must allow the browser origin with the appropriate CORS headers. AlphaX cannot bypass browser security rules.

Defaults and optional policies

WebFetchTransport follows browser security and has these defaults:

Behavior	Default in Web
TLS and proxy	Controlled by the browser; AlphaX cannot replace them.
Protocol metadata	unknown; Fetch does not expose authoritative H1/H2/H3 to Dart.
Retries	Off until AlphaXRetryMiddleware is added.
Authentication	Off until authentication middleware or browser credentials are configured.
Cookies	Browser-managed cookies are off for cross-origin requests until withCredentials: true; an AlphaX in-memory jar is separately opt-in.
Cache and resilience	Off until the corresponding AlphaX middleware is added.

The same AlphaX middleware can be added to Web for policies that do not require native controls:

final client = AlphaXClient(
  transport: WebFetchTransport(),
  middleware: <AlphaXMiddleware>[
    AlphaXAuthenticationMiddleware(
      accessToken: currentAccessToken,
    ),
    AlphaXRetryMiddleware(),
    AlphaXCacheMiddleware(store: AlphaXMemoryCacheStore()),
  ],
);

Retries still require replayable bodies, cache behavior is in-memory unless you provide another store, and browser CORS rules still apply. The Web adapter cannot add certificate pins or an explicit proxy because those controls belong to the browser. See the policy defaults and customization guide for the general policy rules.

Do not combine AlphaXCacheMiddleware with WebFetchTransport(withCredentials: true) unless the application supplies a stable, non-secret cache identityKey for the browser session and changes it or clears the store on logout/account change. Browser-managed cookies are opaque to AlphaX, so the cache cannot discover that identity itself. If browser identity can change without the application observing it, leave AlphaX caching off for those requests.

Cookies and browser credentials

For browser-managed cookies, opt in deliberately:

final client = AlphaXClient(
  transport: WebFetchTransport(withCredentials: true),
);

withCredentials is a browser Fetch setting. Cross-origin servers must also return compatible CORS and credential headers. If the application needs an explicit, transport-neutral in-memory cookie jar, add AlphaXCookieMiddleware(AlphaXCookieJar()) from alphax instead.

Browser boundaries

• H3 is not guaranteed; provider, server, proxy, and network conditions decide the actual protocol.
• Fetch cannot authoritatively report H1/H2/H3, so protocolRequirement is rejected with AlphaXProtocolRequirementException.
• Native file paths, custom trust anchors, SPKI pinning, mTLS, explicit proxy endpoints, and upload progress are unavailable in this adapter.
• Request bodies are buffered before Fetch dispatch because browser Fetch does not provide the AlphaX native streaming-upload contract here.
• Redirect behavior and credential handling remain subject to browser Fetch and CORS rules.

Use alphax_native for Android, iOS, macOS, Linux, and Windows transport adapters. Use alphax directly when you provide another transport.

If a browser limitation is unacceptable, move that operation to a native transport and check its reported capabilities before configuring TLS, proxy, or protocol requirements. AlphaX will fail closed rather than pretending that the browser can enforce a control it cannot observe.

The package is licensed under Apache-2.0 and is published as the separate Web adapter in the current 1.0.0-rc.3 release candidate.