In this guide
LOCALTR / DOCS
Protect and pause a public link
Check Basic Auth behavior, webhook compatibility and how pause affects new incoming requests.
- Environment
- Public sharing · controlled test data
- Evidence scope
- Explanatory app guide; check the steps separately on your installed Mac release.
- Expected outcome
- Check incorrect/correct credentials and a new request while paused separately.
When to use it
Anyone who knows a public address can send requests to your service. Adding a password gives a demo link another access control. You still need application authorization, sample data and protection for sensitive pages.
Test password protection
- Enable password protection in the public URL's access settings. Choose a unique password. Do not reuse your license key or another account's password.
- Open the link in a fresh browser session. It should request Basic Auth credentials. Missing or incorrect credentials produce a
401response. - Open the demo with correct credentials. Successful public access credentials are removed before forwarding to the local upstream.
- If you use a webhook provider, separately confirm it can send Basic Auth. Password protection can also block the provider's callback request.
Pause behavior
Pause the public URL and send a new request. The implementation returns 503 for a new request in that state. Pause does not guarantee instant cancellation of every transfer already in progress. Consider open connections when changing a password or ending access entirely.
Expected result and limits
Incorrect credentials reject a new request; a paused URL does not serve new requests. Browsers can retain Basic Auth credentials, so a fresh session gives a more meaningful wrong-password test. You cannot withdraw a copy of a response someone already saved during a demo. SSO, team roles and IP access lists are not part of this flow. Report unexpected behavior to support with the version, time and redacted status code.
Does a step look different?
Contact support with your app version