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

Re: New work on fonts at W3C

From: Dave Crossland <dave@lab6.com>
Date: Fri, 19 Jun 2009 19:20:47 +0100
Message-ID: <2285a9d20906191120q1905af8cie22bba5ebc929404@mail.gmail.com>
To: Aryeh Gregor <Simetrical+w3c@gmail.com>
Cc: Brad Kemper <brad.kemper@gmail.com>, "Levantovsky, Vladimir" <Vladimir.Levantovsky@monotypeimaging.com>, John Daggett <jdaggett@mozilla.com>, www-style@w3.org

You appear to have shown that Akamai is invisible to browsers for the
puposes of @font-face :)

Regards, Dave

On 19 Jun 2009, 7:14 PM, "Aryeh Gregor"

On Fri, Jun 19, 2009 at 11:29 AM, Levantovsky, Vladimir<
Vladimir.Levantovsky@monotypeimaging.com> wr...
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
a1475.g.akamai.net has address

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:21:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:37 UTC