How To Restrict The Relative Path Of An Incoming Request URI To The Absolute Value In OEG? (Doc ID 1921826.1)

Last updated on OCTOBER 10, 2022

Applies to:

Oracle API Gateway - Version 11.1.1.6.1 and later
Information in this document applies to any platform.

Goal

In OEG 11.1.1.6, when a request with a non existing relative mapped comes through the gateway, it gets mapped to a relative path to which it gets a close match.

For example, if there is a relative path configured in the gateway:

https://<HOST:<PORT>/<VIRTUAL MAP>

A request to "https://<HOST>:<PORT>/<VIRTUAL MAP>xxx" also gets mapped to the above relative path and the corresponding path specific policy gets invoked.

How can the URL be restricted to exactly what is expected?

Solution

	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

Goal

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How To Restrict The Relative Path Of An Incoming Request URI To The Absolute Value In OEG? (Doc ID 1921826.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!