144 reputation
5
bio website bkosborne.com
location
age
visits member for 2 years, 5 months
seen May 23 at 12:07

May
20
awarded  Critic
May
20
awarded  Editor
May
20
revised Why don't browsers respect cache headers for initial page request?
add explanation for the presence of the Expires header.
May
20
comment Why don't browsers respect cache headers for initial page request?
This is not true when when a Cache-Control header is present. It overrides the Expires header for HTTP 1.1 clients. See ietf.org/rfc/rfc2616.txt, section 14.9.3.
May
16
awarded  Supporter
May
16
comment Why don't browsers respect cache headers for initial page request?
Was JUST about to answer my own question as I came to this conclusion as well. I have Google Analytics cookies, one of which changes on each page request, preventing the page from being cached.
May
16
accepted Why don't browsers respect cache headers for initial page request?
May
16
comment Why don't browsers respect cache headers for initial page request?
In Drupal's code, the comment above that header reads: "HTTP/1.0 proxies does not support the Vary header, so prevent any caching by sending an Expires date in the past. HTTP/1.1 clients ignores the Expires header if a Cache-Control: max-age= directive is specified (see RFC 2616, section 14.9.3)." The date specifically is creator of Drupal's birthday.
May
16
comment Why don't browsers respect cache headers for initial page request?
While that's true, that is not true of Drupal's page caching mechanism (it literally caches the entire HTML output and delivers it for "anonymous" traffic) and not really related to my question. My question is about how browsers seem to react incorrectly to the appropriate page cache headers that are set (see the image).
May
16
asked Why don't browsers respect cache headers for initial page request?
Jun
26
awarded  Scholar
Jun
26
comment DNS propogation question with name server change
Bleh - I think the issue was probable that the name server change was done before network solutions actually had a zone file created and pushed out. But on my second attempt, everything went smoothly.
Jun
26
accepted DNS propogation question with name server change
Jun
21
comment DNS propogation question with name server change
So I called NS and they said that there will definitely be a downtime of around 1 to 2 hours during a name server change from one nameserver to another. Very upsetting. This must be something specific to Network Solutions.
Jun
21
comment DNS propogation question with name server change
Err didn't check the error code (doh!), but when looking up the domain in network-tools, it would give me some sort of generic error indicating that it failed to lookup the dns records for the domain.
Jun
19
awarded  Student
Jun
19
asked DNS propogation question with name server change