Using OAM Accessing Protected Resource Gives 400 Bad Request

(Doc ID 2386350.1)

Last updated on MAY 18, 2018

Applies to:

Oracle Access Manager - Version and later
Information in this document applies to any platform.


Using OAM :

While accessing protected resource through webgate, getting the 400 Bad Request error below:

The issue can be reproduced at will with the following steps:
This is how to repeat the issue:

Open browser and put ##.##.##.###:7777/console , It will show error message as:"Bad Request
Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit."




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms