Navigator Service

The WebSphere Portal Server has Navigator Service that allows you to configure how your portal page (By that i mean HTML generated by portal) gets cached in users browser as well as proxy server. It lets you configure value of Cache-control and Expires header.


# Cache expiration time (in seconds) for the portal internal cache for the
# unpersonalized and unauthenticated portal page.
# (values <= 0 are automatically replaced with the default)


# Default: 60
#public.reload = 60


# The cache expiration time (in seconds) for caches outside of portal server
# and for unauthenticated pages only.
# These caches must adhere to the HTTP 1.1 specification (RFC 2616)
# and specifies the time when HTTP caches should drop the response.
#
# This value will be used as a maximum value for the cache expiry time and
# as a global default value for unauthenticated pages.
# In case the setting remote.cache.expiration is also set to a value
# greater than or equal to 0 the minimum value of both settings will be used.
#
# Note that portal may reduce the cache lifetime or may reduce the cache scope
# (public, private) or may switch off the overall cacheability of page
# while processing a request.
# So this value might not be static for all responses to requests
# to unauthenticated pages.
#
# The response of portal server will set the following header fields:
# - The 'Expires' header with the expiry time added to the
# system date & time of the portal server
# - The 'Cache-Control : max-age =' header with the expiry time as its parameter

# Default: 60
#public.expires = 60


# The remote cache expiration (in seconds) for caches outside of portal server
# and for authenticated as well as for unauthenticated pages
# These caches must adhere to the HTTP 1.1 specification (RFC 2616)
# and specifies the time when HTTP caches should drop the response.
#
# This value will be used as a maximum value for the cache expiry time
# for unauthenticated and authenticated pages.
# The global default value for authenticated pages will be 0.
# In case the setting public.expires is also set to a value
# greater than or equal to 0 the minimum value of both settings will be used
# as the global default value for unauthenticated pages.
#
# Note that portal may reduce the cache lifetime or may reduce the cache scope
# (public, private) or may switch off the overall cacheability of page
# while processing a request.
# So this value might not be static for all responses to requests
# to unauthenticated and authenticated pages.
#
# The response of portal server will set the following header fields:
# - The 'Expires' header with the expiry time added to the
# system date & time of the portal server
# - The 'Cache-Control : max-age =' header with the expiry time as its parameter

# Default for full page responses (in seconds)
#remote.cache.expiration = 10800


# The remote cache information for fragment responses (i.e. responses which do
# not refresh the entire page but single page parts only, e.g. a single portlet).
# The specified value will be used as a maximum value for the cache expiry time
# (i.e. a fragment response will never be cacheable longer than the specified value
# even if the fragment itself specifies a value that is greater than the threshold
# specified here).
#
# If an addressed fragment does not specify an expiry value the portal server will
# use the default 0 i.e. the response will not be cacheable.
#
# Special values:
# - Specify a value of -1 to indicate that fragment responses should not underlie a
# a certain treshold.
# - Specify a value of 0 to prevent fragment caching.

# Default for fragment responses (in seconds)
#remote.cache.expiration.fragment = -1


# The default remote cache information for model feeds (typically ATOM responses
# carrying model data. The supported models are content model (identifier "cm"),
# navigation model (identifier "nm"), layout model (identifier "lm"), and portlet
# model (identifier "pm"). If no value is provided the feed expiry will default to 0.

# Default for feeds (in seconds)
#remote.cache.expiration.feed.cm = 60
#remote.cache.expiration.feed.nm = 60
#remote.cache.expiration.feed.lm = 60
#remote.cache.expiration.feed.pm = 60


# The vary response header indicates the set of request-header fields
# that fully determines whether a cache outside of portal is permitted
# to use a response to reply to a subsequent request.
# These caches must adhere to the HTTP 1.1 specification (RFC 2616).
#
# The response of portal server will set the following header fields:
# - The 'Vary' header with the specified parameter
# If more than one request-header field shall be referenced as the parameter value
# it must be provided as comma separated list like the original vary header
# as specified in the HTTP 1.1 specification.

# Default for full page responses
#vary = User-Agent, Cookie


# The vary response header for fragment responses (i.e. responses which do not
# refresh the entire page but single page parts only, e.g. a single portlet).

# Default for fragment responses
#vary.fragment = User-Agent


# Specifies whether the unauthenticated (anonymous) user always has a session.
# This may be desirable because a portlet requires a session for
# anonymous users. However, remember that having a session forbids
# any HTTP proxy to cache the response.

# Default: false
#public.session = false

3 comments:

srjwebsolutions said...


We are leading responsive website designing and development company in Noida.
We are offering mobile friendly responsive website designing, website development, e-commerce website, seo service and sem services in Noida.

Responsive Website Designing Company in Noida
Website Designing Company in Noida
SEO Services in Noida
SMO Services in Noida

Vikas Chaudhary said...

Battery Mantra is Authorized exide car battery dealer in Noida and Greater Noida. We are providing our service in Indirapuram, Delhi, Ashok Nagar.

Exide Battery Dealer in Noida
Battery Dealer in Noida
Authorized Battery Dealer in Noida
Car Battery Dealer in Noida
Car Battery Dealer
Exide Battery Dealer

EG MEDI said...

Egmedi.com is online medical store pharmacy in laxmi nagar Delhi. You can Order prescription/OTC medicines online.
Cash on Delivery available. Free Home Delivery


Online Pharmacy in Delhi
Buy Online medicine in Delhi
Online Pharmacy in laxmi nagar
Buy Online medicine in laxmi nagar
Onine Medical Store in Delhi
Online Medical store in laxmi nagar
Online medicine store in delhi
online medicine store in laxmi nagar
Purchase Medicine Online
Online Pharmacy India
Online Medical Store