OAM: Why are Response Codes to Redirect OAM Server are HTTP 200 or HTTP 302 when Requesting Protected Web Site?
(Doc ID 2553154.1)
Last updated on OCTOBER 22, 2019
Applies to:Oracle Access Manager - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note
- A web site is protected by Oracle Access Manager (OAM) and WebGate. The user's request to a protected web site will be handled by a same Authentication Scheme, but the HTTP response for OAM redirection may be difference depending on URL query parameters.
- When the request URL is short, the client browser that requested the protected web site is redirected to the OAM server by HTTP response code 302.
- When the request URL is long, the client browser that requested the protected web site receives the HTTP response code 200 and redirects the OAM server by POST method, not GET method;
Why does the different response happen?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document