The welcome page is the cheapest way to answer the question every new proxy user asks first: "is my device actually going through Fluxzy?". A short, recognisable HTML reply on a reserved hostname removes that uncertainty in a single browse and frees you to focus on the actual captures.
Reach for mountWelcomePageAction when you want a deterministic, friendly response that proves the client is actually going through Fluxzy. It removes any ambiguity from the first browse a tester does after configuring proxy settings.
Good fits:
fluxzy.local or proxy.test.This action takes no settings, so combine it with a hostFilter or a path based rule to control exactly when the welcome page appears.
Reserve a memorable hostname that a tester can type from any browser to confirm the proxy is intercepting traffic.
rules:
- filter:
typeKind: HostFilter
pattern: fluxzy.local
actions:
- typeKind: MountWelcomePageAction
Useful when you share the proxy with other tooling. The welcome page only triggers when someone hits the exact onboarding URL.
rules:
- filter:
typeKind: FilterCollection
operation: And
children:
- typeKind: HostFilter
pattern: proxy.test
- typeKind: PathFilter
pattern: /welcome
actions:
- typeKind: MountWelcomePageAction
Reply with fluxzy welcome page
Evaluation scope defines the timing where this filter will be applied.
dnsSolveDone This scope occurs the moment fluxzy ends solving the DNS of the remote host
mountWelcomePageAction
This action has no specific characteristic
The following examples apply this action to any exchanges
Reply with fluxzy welcome page.
rules:
- filter:
typeKind: AnyFilter
actions:
- typeKind: MountWelcomePageAction
View definition of MountWelcomePageAction for .NET integration.
The following actions are related to this action:
Not through this action. If you need a branded page, host static files locally and use serveDirectoryAction or return your own payload with mockedResponseAction.
Only if you reach it over HTTPS. On plain HTTP the action works immediately, which is why it pairs well with mountCertificateAuthorityAction during first time setup.
It is harmless but noisy. Scope it to a hostname or path you control so it does not interfere with real captures.