Probe path for Dynamic Site Acceleration not accepted, but can access it using PowerShell Invoke-WebRequest

Question

Probe path for Dynamic Site Acceleration not accepted, but can access it using PowerShell Invoke-WebRequest

Sven Erik Matzen 91

I am trying to setup a CDN endpoint for "Standard Akamai" (also tried with Standard Verizon) and "Dynamic Site Acceleration". This type of optimization demands a "Probe path" which should point to a file that "is publicly accessible and its size is approximately 10 KB" - so, I uploaded a simple text file with 10 KByte and content from a "lorem ipsum" generator and placed it under "/probe/probe.txt".
I've specified "/probe/probe.txt" as the probe path and the "Add an endpoint" dialog in Azure Portal tells me that the "Probe URL" is "http://www.sdx-ag.website/probe/probe.txt
" (all entered here with copy&paste, so there is no typo in the URL).

Azue now telle me "We couldn't retrieve the input probe. Please verify that it is publicly accessible and its size is approximately 10 KB." ... have a look at the URL with PowerShell (or any browser):
Invoke-WebRequest -uri http://sdx-ag.website/cdncheck/check.txt -Method get
StatusCode : 200
RawContentLength : 10000

So: the probe is there, it is definitely accessible using http and https, but the azure portal does not accept it.

It must be something very stupid, but: what am I doing wrong?

ChaitanyaNaykodi-MSFT 27,481 Reputation points Microsoft Employee Moderator

2022-04-15T23:01:05.18+00:00

Hello @Sven Erik Matzen , Welcome to the Microsoft Q&A forum. If I understand it correctly you have also created a support ticket with us for this scenario. I will co-ordinate with the support engineer in this case to help expedite the resolution. Thank you!
Sven Erik Matzen 91 Reputation points

2022-04-19T06:21:36.383+00:00

Hello @ChaitanyaNaykodi-MSFT . Yes, I did create a support ticket after I saw that some people are following this question, but not answering it - so I assume this to be an "uncommon" problem that might not be as easy as simply not using a specific character in the URL.

Your answer

ChaitanyaNaykodi-MSFT 27,481 Reputation points Microsoft Employee Moderator

2022-04-15T23:01:05.18+00:00

Hello @Sven Erik Matzen , Welcome to the Microsoft Q&A forum. If I understand it correctly you have also created a support ticket with us for this scenario. I will co-ordinate with the support engineer in this case to help expedite the resolution. Thank you!
Sven Erik Matzen 91 Reputation points

2022-04-19T06:21:36.383+00:00

Hello @ChaitanyaNaykodi-MSFT . Yes, I did create a support ticket after I saw that some people are following this question, but not answering it - so I assume this to be an "uncommon" problem that might not be as easy as simply not using a specific character in the URL.

Share via

Probe path for Dynamic Site Acceleration not accepted, but can access it using PowerShell Invoke-WebRequest

Your answer