This is supported for Azure CDN from Verizon profiles (https://azure.microsoft.com/en-us/blog/announcing-custom-domain-https-support-with-azure-cdn). Also add this support for Azure CDN from Akamai.404 votes
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.3 votes
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.
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.8 votes
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.
Currently purging is just supported by specifying the CDN endpoint. For case where a rewrite rules is used to direct customers to different content based on the CNAME (e.g. by selecting content to return based on host name) it is valuable to have the ability to purge content based on CNAME. Without this capability one needs to create individual CDN endpoints to use for each CNAME that has different content returned based on the CNAME.7 votes
Allow HSTS and HPKP to be enabled on Azure CDN
Currently these values can only be passed through from the origin, which is fine for HSTS but can cause issues for HPKP (as the CDN cert may change, and probably doesn't match the origin cert)3 votes
How do you want HSTS to be enabled on the CDN? HSTS can be enabled on Azure CDN from Verizon Premium by using the rules engine to add the “Strict-Transports-Security” response header. Support for HPKP would likely require customers to provide their own HTTPS certificates. Once support for providing your own certificates is available the rules engine could be used to enabled HPKP support.
1. The current CDN portal provides the required information, but it would be good to have something in the form of an Dashboard, which can provide an complete view of the performance and utilization.
2. Region/Country wise cache status and the hit and miss ration is good to have to understand the traffic and to be aware of the performance from the different regions.7 votes
Give free a CDN that is ready for use, except for some parameters to be specified and the necessary files to be uploaded. Something like a template.
The videos where experts give lectures are only for other experts to applaud. The majority of your prospective clients are businessmen, educators, etc., who do not want to become experts in IT and do not have the time.1 vote
What specific use case scenarios are you looking for this capability? For a # of end-to-end scenarios in Office 365 (e.g. Office 365 Video) we already enable CDN seamlessly without any user interaction needed or additional cost.
Allow changing pricing their from Verizon Standard to Verizon Premium and vice versa28 votes
API is needed to add new rules (e.g. Country Filtering, Token Auth, etc.) for newly added content.
Use case: User adds new video content in CMS where he is able to block this video in some regions.18 votes
Work has started on both moving capabilities that are only available in the CDN Supplemental Portal (e.g. rules engine) into the Azure Portal and also providing API’s to support all of these features. This work will be done in multiple phases over the next several months.
Currently, I have to wait for hours to get a domain certified, when I have a valid certificate in possession. I would like to allow the ability to upload a certificate per custom domain, or per endpoint and then associate to a custom domain.8 votes
This is planned work and will be done via integration with Azure Key Vault.
Allow user created rules for WAF.24 votes
I'm using Akamai General Web Delivery. Its seems fine but Purge all and on the images files specific have not able the set Leverage Browser Caching (expire headers). Its maybe easly be on the Azure control panel.2 votes
Both of these capabilities are in our backlog for making available via Azure CDN from Akamai later this year.
There is no way I can purge AKAMAI CDN endpoint fully or with wildcard which is best fit for our project.83 votes
Support is planned for this later this year.
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
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.
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.5 votes
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.
I'm looking to use Azure CDN to replace a password-protected FTP area. The lack of access control is preventing me using the CDN.7 votes
When browser sends a Range request to CDN, CDN downloads the entire file from origin, then serve the appropriate range to the browser. However, when serving the content range, it does not send the CORS header that is present in the origin, thus breaking cross origin requests.3 votes
Which SKU of Azure CDN are you using – Azure CDN from Verizon or Azure CDN from Akamai. See the following documentation for working with CORS and Azure CDN – https://docs.microsoft.com/en-us/azure/cdn/cdn-cors. If CORS isn’t working after following this documentation please provide us a repro or open up a support ticket so that we can investigate further.
Wants to add CORS headers in HTTP response sending through Azure Akamai CDN10 votes
Add request filtering ability like in AWS WAF4 votes
Enable authenticated access to CDN without the need to change URL or headers. This is especially useful for referencing a static web page in an IFRAME.
Scenario. When user signs in to example.com, we would first redirect users to a non-cached page on CDN cdn.com, which would set the signed cookies, before redirecting back to example.com.
If you are using Azure CDN from Verizon Premium, you can open a technical support case to have this capability setup for you via the rules engine. Overall you would use the token authentication capabilities in Azure CDN from Verizon Premium to accomplish this – https://docs.microsoft.com/en-us/azure/cdn/cdn-token-auth. With token authentication the signed token is sent by default in the query string for your URL’s. The capability you are looking for is the ability to instead have the token sent as a cookie in the client request to the CDN.
We will look at enabling this capability long term without the need to open a support case.
- Don't see your idea?