OAG Support for Non-standard TLDs
Last updated on JUNE 17, 2016
Applies to:Oracle API Gateway - Version 11.1.2 to 11.1.2 [Release 11gR2]
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 .tmcs domain for all of their servers, when trying to create a Connect to URL filter with a URL ending in something like http://hostname.tmcs:port, a connection error is returned ("Invalid URL entered. Please enter a valid URL").
If the URL is changed from .tmcs 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 .tmcs
5) Click finish.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms