OAG Support for Non-standard TLDs
(Doc ID 1677171.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle API Gateway - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1]
Information in this document applies to any platform.
While creating a Connect to URL filter in the OAG Policy Studio, if the URL contains a custom TLD, an Invalid URL error is returned.
For example if organization uses the .yyy domain for all of their servers, when trying to create a Connect to URL filter with a URL ending in something like http://hostname.<domain>:port, a connection error is returned ("Invalid URL entered. Please enter a valid URL").
If the URL is changed from .yyy to .com, the Connect to URL filter is created as expected and URL is valid and the machine is able to hit the endpoint via a web browser.
Steps to reproduce:
1) Open OAG Policy Studio.
2) Configure an OAG Policy.
3) Attempt to create a Connect to URL filter.
4) Set the URL to a value ending in .yyy
5) Click finish.
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