Azure CDN (Verizon) custom rewrite rule invalid origin

Question

I am trying to update 2 rules in Azure CDN Management (Verizon) Recently they update to V4 and the prefix source is no longer coming on the field

Rule 1 -> If http redirect to https Rule 2 -> If url is empty (only root) serve default document index.html

The new rules engine is unable to identify the Source I already try

The old version had the CDN Verizon id hardcoded on the field, maybe this what is missing? how can I find this?

Hi, I'm having similar issue but prepending my regex with the value you've identified still gives the `Source must contain a valid Origin` error. I've read through the documentation on Verizon that agrees with your format (see https://docs.vdms.com/cdn/Content/HRE/F/URL-Rewrite.htm) but I can't get it to work. I've posted here, and wonder if you have thoughts (see https://stackoverflow.com/questions/62093666/what-is-the-correct-azure-cli-command-for-creating-http-rules-on-cdn-endpoints) Thanks — Aiden Dipple, May 29 '20 at 20:26

score 32 · Answer 1 · answered Nov 04 '19 at 20:23

32

Managed to get the correct values by playing around with other options

To get your customer ORIGIN -> Create new rule

-> Origin -> Customer Origin

-> Copy entire line /80*****/***

-> Use this line to populate your origin on the redirect rule

answered Nov 04 '19 at 20:23

7

This definitely works - although it feels ridiculous that this is the path to finding a value for a required field. – J.Wolfe Jun 16 '20 at 16:24
It was selectable from dropdown in previous version of Rules Engine – iyel Nov 05 '20 at 10:54
1

Just to add, this approach only works with the `HTTP Large` platform, not the `ADN` platform. – Adi Unnithan Dec 22 '20 at 21:13
you saved me a ton of time boss! – Jorge Alvarado Apr 28 '21 at 13:01
@AdiUnnithan comment about using HTTP Large is one of the keys here. – Romeo Aug 09 '22 at 09:11

1 Answers1