Closed jonathanpeppers closed 11 months ago
Hi @jonathanpeppers,
Is it still relevant? I can see the attached PR is already green. I suspect you experienced some network-related issues.
This powershell command still fails for me: Invoke-WebRequest -Uri https://dot.net/v1/dotnet-install.ps1 -Method HEAD
The PR linked above is an example of how we worked around it. We'd still be down otherwise, I think.
Hi @mairaw ,
Could you advise on it? I can repro the issue locally, but I am not sure why it returns 403 code on specifying -Method HEAD
param.
@danzhu54 this might be related to thew new WAF policies. Can you check?
Yes, I added HEAD requests to our blocked list but it makes sense to for this request to be whitelisted. Can you try again?
The powershell is working now, thanks!
> Invoke-WebRequest -Uri https://dot.net/v1/dotnet-install.ps1 -Method HEAD
StatusCode : 200
StatusDescription : OK
Content : {}
RawContent : HTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 70180
Cache-Control: public, max-age=300
Content-Type: application/octet-stream
ETag: "1d9dc5aaeafc324"
Last-Modified: Thu, 31 Aug 2023 22:30...
Headers : {[Accept-Ranges, bytes], [Content-Length, 70180], [Cache-Control, public, max-age=300], [Content-Type, application/octet-stream]...}
RawContentLength : 0
We noticed HEAD requests now give a 403:
Our CI started failing, because we have some generic download code that does an initial
HEAD
request, for showing progress of downloads.See: https://github.com/xamarin/xamarin-android/pull/8311