HTML redirection
When a user successfully authenticates, WebSEAL typically uses an HTTP 302 response to redirect the user back to the resource that was originally requested. This process causes problems for applications that rely on HTML fragments as the fragment information is stored locally in the browser and is lost during redirection.
Alternatively, we can configure WebSEAL to enable HTML redirection. HTML redirection causes WebSEAL to send a static page back to the browser instead of a 302 redirect. The browser can then use JavaScript or any other code that is embedded in this static page to perform the redirect. WebSEAL provides the macro LOCATION, which contains the URL for the redirection.
Parent topic: Web server response configuration
Related concepts
- Static server response pages
- Server response page locations
- Content Aware Server Responses
- HTML server response page modification
- Account management page configuration
- Error message page configuration
- Add custom headers to server response pages
- Local response redirection
Related tasks
- Handling the favicon.ico file with Mozilla Firefox
- Configure the location URL format in redirect responses
Related reference