Browser API requests
INSIDE sends browser requests with the relevant session context and handles connection failures, cancellation and browser compatibility.
What it is
INSIDE uses shared browser request handling for its screens and visitor experience. It attaches the available operator or visitor identity and processes responses from the INSIDE API. Some request paths also support cancellation, time limits and an alternative transport when browser compatibility requires it.
Who uses it and why
Operators and visitors use this behaviour automatically while working in INSIDE or chatting. As a developer, you may need to investigate it when website scripts interfere with requests, an integration times out or a session stops working.
Where to find it
There is no separate screen or Settings switch for browser request handling. Connection messages and errors appear through the feature making the request.
For an external browser integration, ask Powerfront to confirm the supported integration contract before implementing request handling.
How it works
INSIDE prepares a request for its API and attaches the available session context. In a visitor chat context, requests can carry visitor identification. In an operator context, requests can carry the operator's current session identity. The receiving operation still applies its own access rules.
The browser normally uses its modern request mechanism. Where this is unavailable, INSIDE can use a compatibility transport.
Some third-party website scripts replace or wrap the browser's request mechanism. If such a wrapper causes a recognised failure, INSIDE can retry that request once through the alternative transport. Only a successful recovery makes later requests prefer the alternative during that page session. If recovery fails, INSIDE does not make that preference permanent.
Where the calling feature supplies a supported timeout or cancellation control, the browser can stop waiting. Timeout and deliberate cancellation are handled differently; cancellation can be suppressed as an expected action rather than shown as an ordinary error.
For certain forbidden responses while the operator is disconnected, INSIDE displays a disconnection message and redirects to sign-in. Other failures can display an access-denied, connection or input error.
Configure it
No website-wide timeout or transport preference is exposed through Settings for this feature. The calling integration determines which request options it uses.
Ask Powerfront to check identity, request options and browser compatibility when investigating a failure. For website-specific problems, include whether the issue occurs on every page or only pages with particular third-party scripts.
Limits and good to know
- Compatibility recovery is not a general retry policy. Normal server errors and failures from the browser's unmodified request mechanism are not retried through this recovery path.
- Timeout and cancellation support vary by request path. Do not assume all browser requests have the same time limit.
- A browser cancellation does not confirm that the server has undone an action already received. Check the result before repeating a change.
- Different request helpers do not necessarily return or report errors in the same way, particularly inside embedded frames.
- Technical errors can be replaced with a general message for operators.
- Older compatibility code does not establish which browsers are supported for your deployment.
Depends on and works with
View all connections as a list
This feature uses
- INSIDE APIRequires
Browser requests call INSIDE API operations, which apply their own input and access rules.
- Logout and remembered computersEnhances
Operator requests can carry the current session identity and react to session disconnection.
- Website domain checks for browser requestsConfigured by
Browser-origin and request restrictions still apply to API requests.
- Visitor identityEnhances
Visitor requests can carry identification for the current visitor session.
Used by
- Website domain checks for browser requestsRelated
Browser requests must satisfy the applicable origin policy as well as their identity checks.
- INSIDE APIRelated
Browser API requests attach available session context and handle response errors.
FAQ and troubleshooting
Why do requests fail only on one website page?
A third-party script on that page may affect browser requests. Ask Powerfront to compare the affected page with a working page and check the failure.
Why did INSIDE send the request again?
A recognised browser-wrapper failure can cause one attempt through the alternative transport. This does not mean INSIDE retries every failed action.
Why was I returned to sign-in?
A forbidden API response while INSIDE considers the operator disconnected can trigger sign-in redirection. Sign in again, then check whether the original action completed.
Does cancelling mean my change did not happen?
No. Cancellation stops the browser waiting, but the server may already have received the action. Check the current state before submitting it again.
Can I increase the timeout in Settings?
There is no general setting here. Ask Powerfront to check the timeout and behaviour of the particular integration or action.