Exact host
api.staging.example.com
Best when the setup belongs to one host only.
Request Filters
Keep Headers Where They Belong.
A debug token meant for staging should never follow you onto an unrelated site. Give each Profile a clear URL scope, verify it, and browse with confidence.
Turn the Page You Are On Into a Scope.
VibeHeader suggests three useful starting points from the current page: the exact host, the parent domain with subdomains, and the current URL prefix. Choose the narrowest scope that fits.
Domain and subdomains
*.example.com
Useful when the same setup spans related hosts.
Current URL prefix
https://api.example.com/v2/checkout*
Use it to keep a header inside one path or API area.
Express the Scope You Actually Need.
Use an exact domain or URL for clarity, a wildcard for a readable pattern, or a regular expression for versioned routes and other advanced cases.
Readable by default
Regex when precision demands it
Test the Exact Request URL.
Paste the URL your app will call—not only the page visible in the address bar. The tester evaluates it against every enabled filter in the current Profile and tells you whether it matches.
- Matched: at least one enabled filter accepts the URL.
- Not matched: the Profile will not modify that request.
- Invalid: fix the filter syntax before depending on it.
Predictable by Design.
Filters use OR
When a Profile has several enabled filters, a request only needs to match one of them.
No filters means all
An active Profile with no enabled filters applies to all supported request types. Add a filter when broad scope is not intended.
Filters travel with the setup
Shared Profiles keep their valid filters and enabled states, so the receiver can review the same boundaries before importing.
Request Filter Details.
What happens when a Profile has no enabled Request Filters?
The Profile applies to every supported request while it is active. Add at least one enabled filter when a header should stay within a specific site or URL scope.
Do multiple filters use AND or OR matching?
Enabled filters in the same Profile use OR matching. A request only needs to match one enabled filter for that Profile to apply.
Which filter types does VibeHeader support?
VibeHeader supports exact domains, full URLs, wildcard patterns, and JavaScript regular expressions.
Can I test a filter before turning it on?
Yes. Open the built-in URL tester, paste an exact target request URL, and VibeHeader shows whether any enabled filter matches.
Are Request Filters included when I share a Profile?
Yes. Valid filters stay with the Profile in a share link, including whether each filter is enabled. The receiver can review them before import.