Oracle Traffic Director Returns '400: Bad Request' On Certain URL
Last updated on NOVEMBER 05, 2016
Applies to:Oracle Traffic Director - Version 18.104.22.168.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.
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