You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The /search pages use Redis as a backend to store user-selected facets. The Redis cache for these facets expires after N minutes. The search results pages should therefore emit proper Cache and TTL information in its HTTP headers, so that any eventual external cachers (such as varnish) could act accordingly to invalidate their caches automatically, without any configuration.
The text was updated successfully, but these errors were encountered:
* BETTER The search results pages emits proper Cache and TTL
information in its HTTP headers, so that any eventual external
cachers (such as varnish) could act accordingly to invalidate their
caches automatically, without any configuration. (closesinveniosoftware#2302)
Reviewed-by: Tibor Simko <[email protected]>
Signed-off-by: Jiri Kuncar <[email protected]>
* BETTER The search results pages emits proper Cache and TTL
information in its HTTP headers, so that any eventual external
cachers (such as varnish) could act accordingly to invalidate their
caches automatically, without any configuration. (closesinveniosoftware#2302)
Reviewed-by: Tibor Simko <[email protected]>
Signed-off-by: Jiri Kuncar <[email protected]>
jirikuncar
added a commit
to jirikuncar/invenio
that referenced
this issue
May 7, 2015
* BETTER The search results pages emits proper Cache and TTL
information in its HTTP headers, so that any eventual external
cachers (such as varnish) could act accordingly to invalidate their
caches automatically, without any configuration. (closesinveniosoftware#2302)
Reviewed-by: Tibor Simko <[email protected]>
Signed-off-by: Jiri Kuncar <[email protected]>
The
/search
pages use Redis as a backend to store user-selected facets. The Redis cache for these facets expires after N minutes. The search results pages should therefore emit proper Cache and TTL information in its HTTP headers, so that any eventual external cachers (such as varnish) could act accordingly to invalidate their caches automatically, without any configuration.The text was updated successfully, but these errors were encountered: