Custom Hostname Verifier Is Not Being Used During Startup
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.5 and later
Information in this document applies to any platform.
Customers report that their custom hostname verifier is not used as they have specified. Requests using the HTTPS protocol after startup use the custom hostname verifier successfully, but requests using the t3s protocol (like administrative traffic using the domain-wide administrative port) while the system is starting do not.
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