Last updated on JUNE 13, 2017
Applies to:Web Cache - Version 10.1.2.3.2 and later
Portal - Version 10.1.4.2 and later
Information in this document applies to any platform.
The parameter ENABLE_ESI_NOCACHE was created in the situation where there are Proxy Servers between the user client (browsers) and the Portal back end server, where those Proxy Servers can cache information and the end users may not see the actual information from he server, but some cached information done by the Proxy Server(s) in the middle.
This setting is NOT used by default.
When used, you are loading more the system, 'cause where such information would be coming from the Proxy Server(s), with such parameter in-place it will go all the way to the Oracle Web Cache, and possibly backend servers ( Portal and database ). The question here is if cache is properly set within the Oracle Portal site, we only would see a minor increase on the connections to the Oracle Web Cache, by using the above setting.
To be sending the "Cache-Control: no-cache" in the request headers (sent from web browser to server), it will force the validation of the resource onto the Proxy. If the client doesn't send such header in the request to the server, intermediate proxies will return a copy of the content if it is fresh (eg, has not expired according to Expire or max-age fields). The Cache-Control reinforces these proxies to validate the copy even if it is fresh.
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