|
|
|
The Additional URL Configuration dialog is where you configure redirect URLs to handle HTTP 500, 400, 405, and 403 error conditions. If any of these errors occur, redirect URLs can send the user to an application or a customized error page for further action.
Redirection to these customized URLs can take place only when enough information about the Identity Provider is provided to the Service Provider. For example, if during a request there is an issue in retrieving certificate information from smkeydatabase, the user is redirected to Server Error URL specified. However, if a request contains an invalid IdP ID, no redirection happens and the HTTP error code 400 is returned to the browser.
The Additional URL Configuration dialog lets you configure redirect URLs for error handling. This dialog includes the following settings:
Specifies the URL where the user is redirected when an HTTP 500 Server error occurs. A user can encounter a 500 error because an unexpected condition prevents the web server from fulfilling the client request. If this type of error occurs, the user is sent to the specified URL for further processing.
Example: http://www.redirectmachine.com/error_pages/server_error.html
Specifies the URL where the user is redirected when an HTTP 400 Bad Request or a 405 Method Not Allowed error occurs. A user can encounter a 400 error because a request is malformed or a 405 error because the web server does not allow a particular method or action to be performed. If these types of errors occur, the user is sent to the specified URL for further processing.
Example: http://www.redirectmachine.com/error_pages/invalidreq_error.html
Specifies the URL where the user is redirected when an HTTP 403 Forbidden error occurs. A user can encounter a 403 error because the URL in a request is pointing to the wrong target, such as a directory instead of a file. If this error occurs, the user is sent to the specified URL for further processing.
Example: http://www.redirectmachine.com/error_pages/unauthorized_error.html
Mode Fields
For each URL, you can select a mode by which the browser redirects the user.
Redirects the user using an HTTP 302 redirect. When the user is redirected to the specified custom error page URL, they are redirected only with a session cookie and no information appended to the redirect URL.
Redirects the user using the HTTP POST protocol. When the user is redirected to the custom error page URL, the following data, if available, is appended to the redirect URL and then posted to custom error page:
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |