Intermittent "Page Not Found"/"Page cannot be displayed" Errors using URL Path Prefix in Site Mapping and Session Binding in Web Cache
(Doc ID 799584.1)
Last updated on MARCH 29, 2019
Applies to:Web Cache - Version 10.1.2.3.0 to 18.104.22.168.0 [Release AS10gR2 to Oracle11g]
Information in this document applies to any platform.
When pages are displayed through WebCache, intermittent "Page cannot be displayed", "Page not found" errors are returned after patching to 10.1.2.3. The Web Cache site mapping using URL Prefix does work consistently.
The required Path Prefix handling was configured in the Web Cache 'Site To Server Mapping' page on the Web Cache Administration page (not the AS Control Administration GUI).
Session binding binding settings use "Default session binding" : Any Set-Cookie / Cookie-based
-- Steps To Reproduce:
OracleAS MT installed on ServerA on port 7778
OracleAS MT installed on ServerB on port 7778
WC installed on ServerA configuration:
-Site definition: ServerA.com : 7778
-Site to server mapping
ServerB:80/prefix1/ -> ServerA:7778
ServerB:80/prefix2/ -> ServerB:7780
ServerB:80 -> ServerA:7778
Use "Default session binding" : Any Set-Cookie / Cookie-based
Two test URLs:
-This request goes to ServerA
-This request goes to ServerB
With the above two URLs, either URL appears to work properly initially. But checking the session details on screen and ultimately the Web Cache event_log confirms that incorrect routing is happening:
The request prefix <ServerA:7778> matches an alias for configured site <ServerA:7778>
Session binding routing to origin server ServerB:7780 (id=0) for site <ServerA:7778>
non-200 OK HTTP status code response code of 404
The issue does not happen in 10.1.2.0.2 and 10.1.2.2 and appears only after patching to 10.1.2.3 which corrected a cookie scoping issue (<bug 5053392>).
The issue does not reproduce if session binding is disabled.
In WC 10.1.2.0.2, cookie is path-based, which may cause duplicate cookie values for the same
cookie name. This is explained and fixed in <bug 5053392>. That is why different cookie path is
observed between 10.1.2.0.2 and 10.1.2.2.
There is a session servlet test available in the default installation environment at http://<yourhost.domain>/j2ee/servlet/SessionExample
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