Oracle Traffic Director Returns '400: Bad Request' On Certain URL
(Doc ID 1966493.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Traffic Director - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
When attempting to access some SOA webservices URL, the HTTP response fails with HTTP status 400 Bad Request and the request fails to be proxied in OTD.
This works fine when OHS is used to fronted the Weblogic SOA but when OTD is used to frontend the Weblogic SOA, this issue may 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