W3C home > Mailing lists > Public > www-style@w3.org > June 2009

Re: New work on fonts at W3C

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Fri, 19 Jun 2009 14:13:08 -0400
Message-ID: <7c2a12e20906191113h49a1e452k441f2d94c32b0763@mail.gmail.com>
To: "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotypeimaging.com>
Cc: John Daggett <jdaggett@mozilla.com>, Brad Kemper <brad.kemper@gmail.com>, www-style@w3.org
On Fri, Jun 19, 2009 at 11:29 AM, Levantovsky,
Vladimir<Vladimir.Levantovsky@monotypeimaging.com> wrote:
> Root strings allow multiple different domains and paths be encoded in the same font resource - specifying all stages (including local drives) in your content development path should work just fine, without updating web font data. And I would be curious to know how Akamai breaks it, since it's supposed to be completely invisible to UA.

Akamai is not invisible to the UA.  For instance, if you visit
microsoft.com, images are served from different domains:
i.microsoft.com, i2.microsoft.com, i3.microsoft.com.  These are
actually aliases for Akamai servers:

$ host i.microsoft.com
i.microsoft.com is an alias for i.toggle.www.ms.akadns.net.
i.toggle.www.ms.akadns.net is an alias for i.g.www.ms.akadns.net.
i.g.www.ms.akadns.net is an alias for i.microsoft.com.edgesuite.net.
i.microsoft.com.edgesuite.net is an alias for a1475.g.akamai.net.
a1475.g.akamai.net has address 72.246.99.40
a1475.g.akamai.net has address 72.246.99.114

Of course, a font that permitted use by *.microsoft.com wouldn't
actually have an issue here, unless the browser follows CNAMEs before
determining whether the restrictions apply (which would make no sense,
AFAICT).  It would be an issue if the site linked directly to
a1475.g.akamai.net instead of using an alias.
Received on Friday, 19 June 2009 18:13:40 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:18 GMT