locked
CORS for fonts on Azure CDN - Standard Akamai doesn't seem to work RRS feed

  • Question

  • Hi there!

    This is a follow up from https://twitter.com/SybreWaaijer/status/810785711666429952

    I'm using Azure CDN - Standard Akamai's services and it works great.

    Unfortunately, I am unable to edit any configuration files — as I do not have web hosting bound to my account (I only use the CDN, for now).

    This leads to an unsolvable (from my side) issue: font files (woff, ttf, etc.) don't have CORS enabled.

    Cheers!

    Thursday, January 5, 2017 11:14 AM

All replies

  • Hi Sybre,

    Currently, only Premium CDN with Verizon has the ability to dynamically add CORS headers from the CDN.

    We hope to bring this capability to standard in the future.

    Let me know if you have any issues enabling this on Premium (if you choose to switch), and I will gladly help.

    Thursday, January 5, 2017 7:59 PM
  • Hi Richard,

    If Verizon were to support HTTP/2, then I'd be more than happy to switch. Is there any news on that?

    Wednesday, January 25, 2017 7:44 PM
  • It is not currently supported. The team is actively working on this feature, and we plan to support it this year.
    Wednesday, January 25, 2017 8:49 PM
  • Hi Richard,

    We are unable to get syntax to change Modify Client Request Header in azure Verizon cdn rule engine. Please post the syntax to change header.

    Saturday, February 18, 2017 12:26 PM
  • Hi Ratnamchoudhary,

    Can you tell me exactly what you're trying to change?

    The syntax is rather straightforward.

    Tuesday, February 21, 2017 9:49 PM
  • Hello

    any update on CORS and Akami?

    Saturday, February 24, 2018 8:56 PM