StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POFirefox max-age based cache expiration behaving weirdly
primarykey
Id
7765172
data
AcceptedAnswerId
7767370
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-14T08:48:11.187
FavoriteCount
0
LastActivityDate
2011-10-14T12:10:29.510
LastEditDate
LastEditorUserId
0
OwnerUserId
995014
ParentId
0
PostTypeId
1
Score
0
ViewCount
818
LastEditorDisplayName
text
Body
Im working on a virtual globe web application which serves a lot of map tiles, and i am trying to tweak the http headers that my server is sending to indicate the browser (Firefox) an expiration time for it to cache these tiles. The way im doing it is through Cache-Control header and max-age parameter. After a few tests, I realized that caching wasnt working for values below 1799 seconds (approximately 30 minutes). Doing some debugging with firebug net panel, I found out that there is a 30 minutes desynchronization between the client and the server clocks. For example, if the server sends this header indicating a 3600 seconds expiration time: <pre><code>Date Fri, 14 Oct 2011 07:46:12 GMT Server Apache/2.2.13 (Fedora) X-Powered-By PHP/5.2.11 Connection close Cache-Control max-age=3600 Content-Length 47864 Content-Type image/jpeg </code></pre> And i browse the cache contents for this request, i get this. <pre><code>Last Modified Fri Oct 14 2011 09:16:16 GMT+0100 (Hora de verano GMT) Last Fetched Fri Oct 14 2011 09:16:16 GMT+0100 (Hora de verano GMT) Expires Fri Oct 14 2011 09:46:11 GMT+0100 (Hora de verano GMT) </code></pre> Note that client times are GMT+1 and server are GMT, so the real skew is about 30 minutes. So, the conclusion i get to is that Firefox is computing the expiration time from the server date header rather than the response arrival date on the client, is this right? If so this is a big issue, cause if i set a expiration of 1 hour, a user in China would never cach, how could i work this around? Thanks in advance.
Tags
<http><firefox><caching><browser><cache-control>
Title
Firefox max-age based cache expiration behaving weirdly
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USKilian Perdomo Curbelo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.