TABLE OF CONTENTS
Browser version
Our application supports modern browsers: current, vendor-supported versions of Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari. For best performance and security, we recommend keeping your browser up to date. Legacy browsers, unsupported versions, embedded webviews, and compatibility modes are not supported.
“Modern browser” refers to a browser version actively supported by its vendor, receiving security patches, and compatible with current W3C/WHATWG web platform standards, including ES2020+ JavaScript, HTML5, CSS Grid/Flexbox, Web Storage, Fetch, WebSockets, and secure HTTPS/TLS connections.
| Browser Features | Reason |
|---|---|
| JavaScript | Basic Site Functionality |
| Cookies | Authentication and Some Site Functionality |
Third-party services and domains
Stack Internal also relies on several third-party services and domains for things like authentication and email communications which may need to be whitelisted by your IT department. For full functionality and the best possible experience, the following resources must be accessible:
| External Services | Domain | Reason |
|---|---|---|
| Stack Internal | *.stackinternal.com | Required for the Stack Internal application. |
| WorkOS | *.workos.com | Required for the Stack Internal login and OAuth flows. |
| WorkOS | *.authkit.app | Required for the Stack Internal login and OAuth flows. |
| Email Communications | Reason |
|---|---|
| @stackoverflow.com | Communications directly with Stack Overflow employees and support channels. |
| @stackoverflow.email | Automatic communications such as product notifications and newsletters. |
| @stackinternal.com | Automatic communications such as registration and password recovery. |
Security Software Requirements
Some customers may have security controls in place such as firewalls and proxies. Security software mush be configured to support the following.
| Feature | Reason |
|---|---|
| Redirect-based SSO | Security software must allow top-level redirects between Stack Internal, AuthKit, and the customer IdP, including the return to /auth/callback. Blocking cross-domain authentication redirects will prevent login. |
| Streaming HTTPS responses | Proxies should allow long-lived/chunked HTTPS responses. Chat reads streamed responses using browser fetch, ReadableStream, and getReader() in the Chat browser client. |
| TLS inspection compatibility | Any TLS-inspection proxy must trust and successfully re-sign all permitted destinations without altering OAuth redirects, cookies, authorization headers, or streamed responses. |
If you have any questions or need help, please open a ticket on our help center or email us at support@stackoverflow.com.