CDN

How can we improve Azure CDN?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. 273 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  9 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make raw logs available for CDN traffic

    If raw logs were made available and posted to blob storage, developers could use them for sub-billing our customers for their usage of the CDN.

    149 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 129 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    Please provide more context on the end-to-end scenario for which you need signed URL support in the Azure CDN.

  4. Make full purge and wildcard purge for AKAMAI CDN

    There is no way I can purge AKAMAI CDN endpoint fully or with wildcard which is best fit for our project.

    110 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow changing of pricing tier

    Allow changing pricing their from Verizon Standard to Verizon Premium and vice versa

    98 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. CDN: Support Vary: Origin header.

    The CDN ignores the Vary: Origin header, and thus the associated Access-Control-Allow-Origin is not emitted either. Even though the underlying blob store does return the correct Vary header, the CDN ignores this (basically breaking HTTP logic) and returns the same response to all users regardless of the origin (X-Cache: HIT) is then returned instead.

    This is basically a flaw, a bug, and an oversight- but I'm not going to pay for Azure support to tell you this.

    Without this functioning properly, the CDN cannot be used to host website resources (such as fonts) since these must all have Access-Control-Allow-Origin headers…

    89 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    Azure CDN by default ignores Vary header except when it is used with Vary: accept-encoding. This is done as the Vary header can easily cause serious cache bloat issues. Long term we are targeting feature to allow users to easily adjust this default behavior.

  7. Test Azure CDN Rule Engine before sending for approval

    At this moment, you cann't test Azure CDN Rule Engine before sending for approval, approval of new Rules takes up to 4 hours. Which make things very difficult.

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    Rule approval is currently automatic with no delay. We will follow up on having the 4 hour approval message you see in the CDN supplemental portal updated to remove this confusion. While approval is automatic it can currently take 90 minutes for updates to propagate to all CDN POPs. Work is under way to significantly reduce this to a much lower value in the next few months.

  8. Wants to add CORS headers in HTTP response sending through Azure Akamai CDN

    Wants to add CORS headers in HTTP response sending through Azure Akamai CDN

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Provide API to access CDN analytic data

    API is needed to access analytic data (e.g. hits, cache/hit ratio, GB usage, bandwidth, etc.)

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow different CDN cache and client cache times for Azure CDN Standard

    Currently the only option is to set the Max-Age header on the content which sets the TTL on the CDN endpoints AND on the clients.

    If we use the Purge API to refresh the CDN content, the clients still have the cached version.

    Akamai has a "downstream-ttl" attribute on the Edge-control header that allows for client expiration customization while letting the "max-age" header set the CDN expiration.

    This way you can set the downstream-ttl to 0 (client always requests to CDN) while CDN can cache the original content until Purged.

    Without this, the Purge command is not entirely useful.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    I’ve updated the title to reflect this is a request for Azure CDN Standard as this is supported via the rules engine in Azure CDN Premium from Verizon. Suppport for this is targeted for availability later this year in CDN Standard from Akamai and Verizon.

  11. Support compression directly from IIS Origin

    Azure CDN adds the Via header when it communicates with origin servers as this is required by HTTP/1.1 - (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html). IIS by default does not apply HTTP compression to requests that have the "Via" header. This prevents gzip compression from working by default with Azure CDN as IIS by default will not compress content when it receives a request with a Via header. This default setting for IIS can be changed by setting the noCompressionForProxies to false.

    This is not intuitive and should "just work". The whole point of having combined services in Azure is that we shouldn't…

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    I significantly updated the title and contents of this request to accurately reflect why compression from an IIS origin does not work with Azure CDN. The CDN does support HTTP/1.1 when communicating with origin servers. We are planning on adding support in the future that will allow one to prevent the Via header from being sent to IIS.

    In the next month we are also targeting to enable one to have the CDN compress files directly – see http://feedback.azure.com/forums/169397-cdn/suggestions/1074433-automatic-http-compression-on-azure-blob-cdn-gzip.

  12. Provide the ability to prevent hotlinking in Azure CDN Standard

    The ability to deny content or serve alternate content when hotlinking is detected, via whitelist / blacklisting referrers.

    This would help us protect our CDN from third-party usage and is something AWS provides already.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    I’ve update the title to indicate that this is a request for Azure CDN Standard. This capability is available to today with Azure CDN from Verizon Premium via the rules engine. Via the rules engine you can match on a specific referer and deny a request or redirect / rewrite the request to a different location.

  13. Request filtering like AWS WAF

    Add request filtering ability like in AWS WAF

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Make another POP location in Moscow, Russia

    Make another POP location in Moscow, Russia

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Is there any plan to implement how to operate Azure CDN by JAVA SDK?

    We are now using JAVA SDK to access Azure service but it seems no api to operate CDN service. We need to use the "query string" function of azure cdn with java, i would like how to define the file name pattern of resource like css or javascript.
    So, we would like to know is there any schedule of this request will be planned? Thanks.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    Yes support for Java SDK is planned. Initial API support for Azure CDN is targeted to be available in December. Java SDK support will follow after this is released.

  16. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. CDN should support ETAGS just like they support last modification date

    When performing a request with 'If-Modified-Since' header, CDN correctly respond 304 if data is not modified. But they ignore equivalent ETAGS directive: IF-None-Match and always return OK 200. They should consider it. Just as described in RFC 7234.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    This is a limitation just with Azure CDN from Akamai. With Azure CDN from Verizon ETag support is enabled by default. Supporting ETags is an optional and not a mandatory header per HTTP RFC. We are working long term to mitigate / remove differences in caching behavior between Verizon and Akamai.

  18. Provide Feedback as to if CDN can reach origin url.

    Right now you need to wait 90 minutes or so (potentially) if you are getting 404 errors on content. It would be nice to have some kind of visual feedback on the endpoint configuration page if the origin url was reachable from Azure.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    With Azure CDN from Verizon it takes up to 90 minutes for configuration for a new CDN endpoint to propagate to all worldwide CDN POPs. For a new endpoint you will get back 404 errors until the configuration has propagated to the CDN POP that you are making requests to. We are working with Verizon to reduce this propagation time and also working with them so that we can deterministically provide feedback via API and UI when this propagation has completed.
    With Azure CDN from Akamai CDN endpoints are typically created in under a minute and the status of via API and UI accurately reflects when endpoint configuration has completed.

  19. cmdlet / API for updating 'Custom caching rules'

    It looks like the only way to update caching rules is via the WebUI, it would be nice if there was a programmatic way of updating custom caching rules, you know devops and all that. cmdlets / api / **** even ARM options

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add Azure Service Fabric Reverse Proxy Port to AKAMAI CDN Allowed Origin Ports

    The Azure Service Fabric Reverse Proxy allows services running in the cluster to be reached from outside the cluster via HTTP(s). The default port for the reverse proxy is 19081.

    Azure CDN (with AKAMAI) allowed origin port list currently does not include that port.

    AKAMAI CDN should include the default reverse proxy port for Azure Service Fabric in the allowed origin port list so that integration can happen right out of the box.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Anton Kucer [MSFT] responded

    Thank you for the feedback. We have confirmed the ability to add this port. We are targeting January 2018 to have this update in place as the Akamai network is currently locked down for this type of update until after the holiday season.

← Previous 1
  • Don't see your idea?

CDN

Feedback and Knowledge Base