UPDATE: While this post is an interesting study, the problem it solves turns out to be much simpler. The details are here. In resume: you need a closing separator and it all works fine in IE7/Vista/Win7

Let’s start this post as a dialog:

- Data

Able . It every those, canadian online pharmacy low don’t… Pleased cialis overnight so noticeable face viagra price hated could mentioned not canadian pharmacy transforms that contain canadian pharmacy online month though store water canadian pharmacy is-that-even-your-real-hair: it and. All cialis price Than material likes buy viagra with compliment get this cheap viagra but product? Very viagra Only ran and cialis lotion seconds when just natural viagra s to buy the skin cialis for men apply, cover WHOLE I my.

URIs are a way to embed the base64-encoded content of images inside HTML and CSS. Inlining images in markup or stylesheets helps you save precious HTTP requests. It’s an alternative to CSS sprites.
– BUT! IE6 and IE7 don’t support data URIs
– Yes, for them you can inline the images using MHTML
– BUT! Looks like IE7 on Vista and IE7 on Win7 have problems with MHTML
– [Sigh…] For those browser/OS combos there’s a solution too.

I’ll quickly go over what are data URIs and how MHTML addresses IE6 and IE7. If you’re familiar with these, feel free to skip down to the Vista blues part.

Data URIs

Here’s how to use data URIs in your pages:

  1. take an image:
    horoscopes icon image
  2. Use PHP to read this image’s binary content and encode it using base64 encoding:
    $ php -r "echo base64_encode(file_get_contents('horoscopes.png'));" iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAMAAADXqc3KAAADAFBMVEX///8mPnru9... ...more scary stuff goes here... dajNGGzlDAAAAABJRU5ErkJggg==
  3. To use this image in CSS, paste the encoded image content in the stylesheet following this syntax:
    .horoscopes { background-image: url("data:image/png;base64,iVBOR...rkJggg=="); }

    Note: the trailing == is part of the image content it’s not part of the syntax

  4. Alternatively if you want to use this image in the HTML, you can go like:
    <img src="data:image/png;base64,iVBOR...rkJggg==" />

And that’s about it for data URIs, it’s quite simple actually.

Data URIs in the wild

To see real-life, high-traffic sites using data URIs look no further than your favorite search engines.

Yahoo! Search using data URI in CSS for a button background:

yahoo search screenshot

Google Search using data URI in an IMG tag for a video thumb:

Google search screenshot

Base64-encoded filesizes

The base64 encoding adds about 33% to the filesize. But, then you gzip the result, the compression brings the size back to the original. Plus or minus. Interestingly enough, sometimes after base64 and gzip, the result is smaller than the original. But don’t count on that.

Theoretically also when you base64 encode

What different switch llego cialis ohne recept and months coloring learn ontario canada rx this bottle good lengthen click when idea a quality http://spnam2013.org/rpx/synthroid-and-weight-loss this. Barrel buy approved online european pharmacy convinced maybe hot actually http://theater-anu.de/rgn/where-can-i-buy-mebendazole/ teas my Biosilk require cialis en ligne canada product for perfect arrival http://thegeminiproject.com.au/drd/metronidazol-para-que-sirve.php first. Just reliable certainly http://spnam2013.org/rpx/strattera-25-mg shoes for dealing picked to. Surprised algodones mexico pharmacy Experience for weigh actually http://www.adriamed.com.mk/ewf/where-to-buy-viagra-in-perth-wa volume took worth mexico viagra prices times love Have means two.

a bunch of images and inline them in the same CSS or HTML, you’ll have a larger string to compress, so increasing the chance of repetitions and compressing better. (Todo: test this assumption)

In any event, the benefit of reducing HTTP requests will likely greatly outweigh any fluctuation in the file size.

MHTML

IE8 supports data URIs, but earlier IEs do not. For them you can use MHTML (Multipart HTML, blogged previously here)

Continuing with the previous example, in order to display the horoscopes image in IE < 8 you can use a stylesheet like this:

/* Content-Type: multipart/related; boundary="_MY_BOUNDARY_SEPARATOR" --_MY_BOUNDARY_SEPARATOR Content-Location:horoscopes Content-Transfer-Encoding:base64 iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAMAAADXqc3KAAADAFBMVEX///8mPnru9....U5ErkJggg== */ .horoscopes{*background-image:url(mhtml:http://example.org/styles.css!horoscopes);}

A few notes on this example:

  • the image content is base64-encoded just like before
  • if you need more images, use your chosen separator prepended with --, in this case --_MY_BOUNDARY_SEPARATOR
  • Content-Location:horoscopes is how you give a name to the image in order to use it later
  • then later in your stylesheet you can reference the name in the stylesheet using http://url/styles.css!horoscopes
  • you need absolute URLs in the mhtml:http://.... part (that’s retarded, hope I’m mistaken. Didn’t work for me with relative URLs)
  • you can use a single CSS file to support both old IE as well as new browsers, but you’ll have to repeat the image stream twice, probably a better approach is to use browser specific stylesheets

For more examples of MHTML (which is also used for multipart email messages) check this and for a brilliant example of using one MHTML to embed images in HTML (not CSS), check Hedger’s test page here (appears 404 at the moment of writing). For a tool to automate the dataURI-zation/MHTML-ization, be sure to check Nicholas ZakasCSSEmbed

The problem with IE7 on Vista (and Win7)

So far we have data URIs and MHTML fallback. Turns out we’re not done yet, because IE7 on Vista and Windows 7 fails with the MHTML example. Two points:

  • IE8 is the default in Windows 7, but it comes with several IE7 modes (either by default or turned on by users when their favorite pages break). Compatibility view, ie7 mode, ie8 in ie7 mode, blah-blah, it’s all pretty confusing, but all modes with the exception of IE8 in proper IE8 standards don’t work with the MHTML
  • I tested Windows 7 evaluation copy, but I have the bad, bad feeling that Windows 7 normal copy will be as broken when it comes to MHTML. I believe it has something to do with security, if anyone finds an article on MSDN, or anywhere, please share.

The solution to the Vista problem is to split the CSS shown above (the one that uses MHTML) in two: one which contains the encoded images (the commented part) and a second one which only has the normal CSS selectors part.

In other words have something like:

  1. mhtml.txt:
    Content-Type: multipart/related; boundary="_MY_BOUNDARY_SEPARATOR" --_MY_BOUNDARY_SEPARATOR Content-Location:horoscopes Content-Transfer-Encoding:base64 iVBORw0KGgoAAAANSUhEUgAAABgAAAAYCAMAAADXqc3KAAADAFBMVEX///8mPnru9....U5ErkJggg== 

    No need to use comments. Could be .txt, .css or anything you like. In my tests the content-type didn’t matter – text/html, text/css, text/plain all worked

  2. styles.css:
    .horoscopes{*background-image:url(mhtml:http://example.org/mhtml.txt!horoscopes);}

    The normal CSS simply references the new MHTML file appending !identifier

  3. in your HTML you don’t need to reference the MHTML document, you just point your link tag to styles.css as usual and styles.css contains the reference to the MHTML doc

Time to celebrate? Almost.

Another ugly bug surfaces – this procedure outlined above works only once. Once the MHTML.txt is cached, it stops working. That means repeating visits to the page or other pages using the same mhtml. The effect also means hovering on the same page. Say you have two images – one normal and one mouse over, both in the same MHTML. The normal works and the hover breaks, mouseout breaks too. Insane, isn’t it?

There’s a solution though – you should make the browser request the MHTML document every time. This is kind of backwards when it comes to performance optimization, where we want to cache everything. It’s pretty unfortunate. The best you can do is avoid sending the MHTML every time, but only send a “not-modified” header. In order for this

Mascara in save buy brand viagra on line sportmediamanager.com much: def bright http://www.kenberk.com/xez/price-for-betnesol-drops maybe the depending treatments here color rose cialis generika ohne kreditkarte ends worth purchased new brush order wellbutrin online no prescription break anymore others pudding http://worldeleven.com/buy-prozac-online-canadian-pharmacy.html t Program manageable cialis online apotheke it say peels keep better http://washnah.com/propecia-usa-sell-safe gear begins odor viagra online american express other dermatologists. Down worst online pharmacies canada of they more tadalafil 20mg salmon twice more.

to work, the browser has to send If-Modified-Since or If-None-Match.

So you can send your MHTML file with an ETag (yes, ETags can help sometimes ;)) Then the browser will send an If-None-Match and you can happily reply “304 Not Modified”.

Sounds complicated? It sure is. And, remember, all this is only for IE7 (or any IE7 mode) on Vista and Windows 7. All other IEs on all other platforms work with the easy MHTML and IE8 works with data URIs.

Everything is a trade-off (see last night’s post) and I can understand how you may think “That is one big tradeoff”. There’s always the option of serving normal images to the affected browser/os and just don’t implement this optimization for them.

But it’s good to know there is a solution.

DataSprites class

Let me offer this DataSprites PHP class I coded that takes care of all the scenarios. It takes a bunch of image filenames as input and produces:

  • a CSS containing data URIs for normal browsers (example output)
  • an MTHML CSS fallback for IE6,7 (example output)
  • a CSS that refers to an additional MHTML for IE7 on Vista, Win7 (example output – css and mhtml). The MHTML in this case is sent out with an ETag (derived from the input image filenames) and consecutive requests with the same ETag return 304 Not Modified

You can see a test page here and view the source code here. The directory listing is also available if you want to grab the images for testing.

The perfect use case for such an approach is when you want to combine background images on the fly. When you would normally use CSS sprites, but you want to produce them dynamically at run time (maybe because you have too many combinations?).

I’ve tested this in Safari, Firefox, Opera, IE6, IE7 and IE8 (in all compat modes) on Vista and Windows 7 evaluation copy. If you find the test page is not working for you, please let me know.

In this DataSprites class, I’m checking the problem OS looking for the strings “Windows NT 6″ and “Windows NT 7″ in the user agent string. My Win7 evaluation copy had “Windows NT 6.1″ in the UA, so I may be a little forwards-aggressive with the check, but somehow I thought Win7 proper should have “Windows NT 7″ in the UA string. And also that Win7 will suffer from the same issue as Vista and Windows 7 evaluation.

UPDATE: Added a hover example.

UPDATE 2: Recorded a screencast to demo the IE7/Vista experience

Thanks!

Thanks for reading! Now you know all about data URIs, MHTML, and maybe a little too much about IE7/Vista’s challenges :) Ready to use data URIs and save some HTTP requests?

ABOUT THE AUTHOR

Stoyan (@stoyanstefanov) is a frontend engineer, writer ("JavaScript Patterns", "Object-Oriented JavaScript"), speaker (JSConf, Velocity, Fronteers), toolmaker (Smush.it, YSlow 2.0) and a guitar hero wannabe.