Caching PHP-generated pages

▼ For years, I always used to include an If-Modified-Since header in my PHP scripts in order to allow their output to be cached by web brow­sers. Turns out, it takes a bit more work.

The idea is that the HTTP server tells browsers when the page was last modified when browsers request a page. Then, when they request the same page again later, the browser can say "only send me the page if it's been modified since <date>". If the page has been changed since <date> the server sends over the page. If the page is still the same, it just sends a 304 response code, "Not Modified". The browser then displays the page from its cache.

(If the browser doesn't supply an If-Modified-Since date, the page is always sent.)

The Apache HTTP server can handle all of this for HTML and other static files. But PHP scripts generate output on the fly, so the concept of a last modified date doesn't really apply, so PHP-generated pages are always sent, even if they are the same as during an earlier visit.

Of course many PHP scripts generate output based on what's in a database, and as long as the contents of that database don't change, there's really no need to run the script again. But the script itself has to be smart enough to handle this. I had a look at this page and then came up with the following.

First, we determine what the last modified date should be: the last time the script itself was changed, or the last time the database was changed, whichever was more recent:

<? $mtime = getlastmod(); $result = mysql("mydb", "select max(unix_timestamp(createts)) as uts from mydb") if ($row = mysql_fetch_array($result) && $row[uts] > $mtime) $mtime = $row[uts];

Then, we check against the If-Modified-Since header supplied by the browser. If the our last modified date is older or the same as the browser's, we send the Not Modified response and call it a day.

$htime = strtotime($HTTP_IF_MODIFIED_SINCE); if ($htime && $mtime <= $htime) { header("HTTP/1.0 304 Not Modified"); exit(); }

(Of course there's some more error checking here and there.)

If the script is still running, the browser had an old version of the page so we're going to send over the latest version. Before we do that, we generate a Last-Modified date so the browser knows what to say in its If-Modified-Since header the next time.

header("Last-Modified: " . date("r", $mtime));

In Safari, it looks like entering a URL in the URL/search bar doesn't use If-Modified-Since, but clicking on a link does. This is now a good deal faster for me. It should help even more for people on slow links or far away from the server.

Permalink - posted 2013-07-18

iOS 7, new iPhone screen sizes and insta-deletion

▼ Decisions, decisions: update your iOS apps now for iOS 7 and be ready on day one, or wait until new iPhones and iPads arrive and incorporate support for a possible new screen size/resolution in the update?

On the Tapadoo blog, Dermot Daly writes that when the iPhone 5 came around, his clients were initially reluctant to spend money updating their iPhone apps to support the bigger screen, but the letterboxing that happened with the unupdated apps made those an ❝insta-delete❞ for many users. He thinks that iOS 7 will play out in much the same way.

(On episode 63 of the Amplified podcast, Dan Benjamin argues that people won't delete apps unless an alternative that does support the bigger / higher resolution screen or new aesthetic is available, and I certainly agree with that.)

However, what if Apple once again releases iPhones (or iPads) with a different screen size/resolution? Unless you really want to have your update ready on day one, it may be prudent to wait for that shoe to drop before finalizing a big update, and certainly start laying the groundwork for another screen size now.

It will be very interesting to see how regular users react to the big changes in iOS 7. It could be like a website redesign, where lots of people complain. But I think even regular users will know there are big changes, and either decide to stick with the old iOS or upgrade understanding that things are going to be different. I also think that old apps won't stick out like a sore thumb immediately like what happened on the iPhone 4's higher resolution display, or to a lesser degree, on the iPhone 5's taller screen. But as users spend more time with updated apps, the older ones will start worse and worse. So there's probably a grace period before that deletion impulse kicks in.

Permalink - posted 2013-07-17