locked
Failure Error When Trying to Purge RRS feed

  • Question

  • I have tried to purge image resources from our CDN multiple times in the last 24 hours and get a failure message each time with the error code "BadRequest" and the message "That action isn't allowed in this profile." I am using an administrator account so what would be causing this issue?
    Wednesday, February 15, 2017 8:29 PM

Answers

  • We looked at the failures that you had provided information on via Twitter. The failure that you saw on 2-14-2017 was a result of one of your content paths for purge not being specified as a relative path. The path just began with "t/images/...". To be a valid relative path it needed to start with "/t/images/..." We are working on an update to add this validation to purge requests done from the Azure portal.

    The other failures all occurred during a scheduled 1.5 hour CDN maintenance window that occurred between 2/15/2017 7pm to 8:30 pm (UTC). Notification of this maintenance window was provided directly in the Azure portal. During this maintenance window there was no interruption to traffic delivery but you would not have been able to successfully issue purge requests. This maintenance was a one time event as a result of a critical infrastructure upgrade on Verizon.


    • Edited by Anton Kucer - MSFT Thursday, February 16, 2017 3:24 AM
    • Marked as answer by alaynah Thursday, February 16, 2017 3:24 PM
    Thursday, February 16, 2017 3:08 AM

All replies

  • Hello,

    Could you tell me which CDN Profile (Verizon/Akamai) you are using, and what path you are trying to purge? Are you using the API or Portal UI?

    I ask since some types or purge, like root purge, is not available in Akamai.

    Wednesday, February 15, 2017 10:30 PM
  • We looked at the failures that you had provided information on via Twitter. The failure that you saw on 2-14-2017 was a result of one of your content paths for purge not being specified as a relative path. The path just began with "t/images/...". To be a valid relative path it needed to start with "/t/images/..." We are working on an update to add this validation to purge requests done from the Azure portal.

    The other failures all occurred during a scheduled 1.5 hour CDN maintenance window that occurred between 2/15/2017 7pm to 8:30 pm (UTC). Notification of this maintenance window was provided directly in the Azure portal. During this maintenance window there was no interruption to traffic delivery but you would not have been able to successfully issue purge requests. This maintenance was a one time event as a result of a critical infrastructure upgrade on Verizon.


    • Edited by Anton Kucer - MSFT Thursday, February 16, 2017 3:24 AM
    • Marked as answer by alaynah Thursday, February 16, 2017 3:24 PM
    Thursday, February 16, 2017 3:08 AM
  • Thank you Anton, I ran another purge this morning and that went through successfully! I had not seen the notification and will look for it if I run into issues again.
    Thursday, February 16, 2017 3:24 PM