locked
Exact example of LITERAL match 301 redirect. Nothing working, terrible interface, slow and painful RRS feed

  • Question

  • Come on Azure/Microsoft. This has got to be the absolute worst interface for dealing with the most critically important aspect of migrating to a CDN.

    How about some documentation outlining in detail the most likely needed rule? A 301 redirect from old URL to new?

    I'm entering in the following:

    <rules schema-version="2" rulesetversion="177" rulesetid="1012137" xmlns="http://www.whitecdn.com/schemas/rules/2.0/rulesSchema.xsd">
      <rule id="2071354" platform="http-large" status="active" version="0" custid="B2AF6">
        <!--Changed by userId: 238 on 06/01/2019 06:19:11 AM GMT-->
        <description>/fr/telephones/detail/a8 (edited by appsupport INC0542989)</description>
        <!--If-->
        <match.always>
          <feature.url-redirect code="301" pattern="/80B2AF6/tmsprodstatic/fr/téléphones/detail/a8" value="https://%{host}/fr/phones/galaxy-a8" />
        </match.always>
      </rule>
    </rules>

    I have hundreds of these to enter. I've entered a bunch in this interface from 1998 and waited 4 hours only to find out the rules do not work. They seem to be simply ignored.

    What I would expect this rule to do is take any incoming request where the path is "/fr/téléphones/detail/a8" and redirect that to the requesting host and path of "/fr/phones/galaxy-a8".

    But that's not what happens. There is no redirect. 

    I've got two domains, I have rules to force www and https. And then I need about 200 literal match redirects. I'm sure many others are trying to do the same.

    Sunday, June 2, 2019 5:18 PM

All replies

  • Hi, 

    I have shared your feedback with the Product Group. Also, I will try this out and get back to you on the redirection part. 

    Regards, 

    Msrini

    Monday, June 3, 2019 5:35 AM
  • Hi, 

    Can you provide me the direct URL so that I can test and get this sorted. 

    Please drop an email to azcommunity@microsoft.com with your subscription ID, along with the URL which you are trying to create the redirection rule. 

    Regards, 

    Msrini 

    Monday, June 3, 2019 7:04 AM
  • Done.

    Just for reference:

    2 sample redirects I am trying to make:

    requests for Path /fr/téléphones/detail/a8 (does not exist in new site) should be redirected to: https://%{host}/fr/phones/galaxy-a8 
    requests for Path /phones/detail/samsung-galaxy-s9 (does not exist in new site) should be redirected to: https://%{host}/fr/phones/galaxy-a8/en/phones/samsung-galaxy-s9

    What I really need is instruction of exactly how to use the CDN interface to add the working redirects (400 of them). The CDN endpoint is pointing at a storage container static website $web blob. The old site URLs have been changed on our new site.

    Monday, June 3, 2019 7:01 PM
  • Hi, 

    The rules would have to be implemented one by one into the portal, but one thing we can do is expedite the rule approval process with AppSupport so we are left with only propagation times. 

    So we can get some tests in the account, here's some documentation covering redirects - https://docs.vdms.com/cdn/re3/#HTTP_Rules_Engine/URL_Redirect.htm?Highlight=redirect

    I see you have raised a support ticket - 119052224000672 and you are working with Support engineers. The above link has general guidelines on creating a redirection rule. 

    Let me know if you need any further assistance from my end. 

    Regards, 

    Msrini

    Wednesday, June 5, 2019 8:48 AM