Loading...
 
Skip to main content

Fixed HTTP Expires Header is in year 1981

  • Tracker item actions
Trackers
Items
Status
Closed
Subject
Fixed HTTP Expires Header is in year 1981
Version
10.x
Category
  • Error
Feature
Performance / Speed / Load / Compression / Cache
Resolution status
Won't Fix
Submitted by
lkordix
Lastmod by
Nelson Ko
Rating
(0)
Description

Hello,

we have noticed a problem within some HTTP response headers where the value the Expires-key is hard set to "Expires: Thu, 19 Nov 1981 08:52:00 GMT". This causes some browsers to not be able to cache the page and cause performance issues.

We first experienced this with requests to article_image.php?image_type=topic&id=<someid>

Then we noticed, that the index.php has this Expires header value set, too. And unfortunately it's the same on dev.tiki.org, too.

Could you please have a look?

Thanks in advance!

Lars

Solution

This is the default TIki behavior as a lot of people complain they see stale content. But there is a way to get around this.

Under Admin...Home...Performance, look under the Sessions tab. There is a setting for Cache-Control header (no session):. This sets the behavior for caching for non-logged in users. However, for this to work, Silent Sessions will also have to be activated (this is also on the same tag).

For example, if you want to set the maximum age that caches should obey to one day, the header setting can be: max-age=86400, public

Admittedly the feature can be improved to provide more fine grained control over what parts of the site, etc... but that would be a separate feature request.

Hope this works well enough for you.


Importance
7
Easy to solve?
4
Priority
28
Demonstrate Bug on Tiki 19+
Demonstrate Bug (older Tiki versions)
Ticket ID
4793
Created
Tuesday 08 October, 2013 07:10:36 UTC
by lkordix
LastModif
Saturday 19 October, 2013 23:31:38 UTC


Show PHP error messages