Azure CDN – Standard Microsoft: Rules Engine for http to https redirection

Hello everyone,
Sorry for the delayed response as i was away from work for sometime.
 
Checked the updates here internally and understood that the fix had been pushed and the http to https redirection rule shall work, however you need to use the "RequestScheme" rule condition instead of "RequestMethod" as suggested by Josh_Gallagher in his comments above. Thanks Josh_Gallagher for sharing details.
 
As indicated in this article, this feature is still in preview as such, it may be subject to frequent changes, and may not be suitable for production deployments yet.

Okay, so trying this again it seems that if I use only the "RequestScheme" condition mentioned in my last comment, and not the "GET" condition, it works. It is also possible that when I tried to have both conditions in the rule yesterday I did not leave enough time for the policy to propagate before testing it. This time my successful tests were half an hour after applying the policy. Immediate testing had still shown that it didn't work.

This seems to have been resolved now. I just completed the steps without error today. However, this then resulted in an infinite redirect as it seemed to be matching HTTPS as well as HTTP. Given that the rule only matches GET verbs and ignores the scheme, I guess this was to be expected. I tried to guess how to add another condition:

$protocolCondition = New-AzCdnDeliveryRuleCondition -MatchVariable 'RequestScheme' -Operator Equal -MatchValue "HTTP"
$ep.DeliveryPolicy[0].Rules[0].Conditions.Add($protocolCondition)

However, after saving the endpoint there seemed to be no change in behaviour. Unfortunately then trying this:

$ep.DeliveryPolicy = $null
Set-AzCdnEndpoint -CdnEndpoint $ep

...did not remove the policy. When retrieving the endpoint again and inspecting it, the policy is still present with all the same conditions and rules. I think Set-AzCdnEndpoint decided that as I wasn't providing a DeliveryPolicy I must not be wanting to alter the current state.

The following mechanism did clear out the policy and at least remove the infinite redirect problem (though no solution for HTTP => HTTPS redirect):

$ep.DeliveryPolicy.Rules.Clear()
Set-AzCdnEndpoint -CdnEndpoint $ep

Braja it would be enormously useful if you could indicate the correct syntax for matching only HTTP requests in the conditions. Thanks!

Thank you Braja!  We're holding up a production rollout of a site, so this fix will be much appreciated.

Hello technetColmar & jcrosbyrwb ,

There was a fix planned to release for this issue in next 2-3 weeks, you can expect this to work by then. I'll update this thread once the fix is deployed for it.

Hello jcrosbyrwb & technetColmar ,

I'm able to reproduce this error, seems like something has changed, I'm checking more on this internally, will post further updates on this.

Hello!  We keep getting the following error when trying to run the Set-AzCdnEndpoint cmdlet for a Standard Microsoft CDN Profile.  Tested on Az.Cdn 1.3.0, 1.3.3, and current Cloud Shell.

Set-AzCdnEndpoint : Operation returned an invalid status code 'BadRequest'

With the following in the 400 response:

"message": "A type named 'Microsoft.Azure.Cdn.Models.DeliveryRuleUrlRedirectActionParameters' could not be resolved by the model. When a model is available, each type name must resolve to a valid type."

Are you able to reproduce this?

varadasandeep you're welcome.

<Updating the answer as per the latest release>

To remove the policy from an endpoint, you can do a Get-AzCdnEndpoint to retrieve endpoint data. Once you get the endpoint data, make a call to clear the delivery policy rules, then do Set-AzCdnEndpoint with the updated endpoint data.

E.g.

Thanks, This document has helped me a lot.

But, is there a way to remove the policy that has been attached.