Forum Discussion

Noel Burgess's avatar
Noel Burgess
Steel Contributor
Mar 19, 2020

Your request has been blocked

When attempting to research setting GP by script, I came across this page: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn789190(v=ws.11) 

 

On that page, I found this paragraph:

 

Additional considerations
For more information about scripting, see the Group Policy Script Center (https://go.microsoft.com/fwlink/?LinkID=66013).
  


But clicking that link produced this response: 

 

Neither of the reasons quoted can apply. Can anyone reproduce this behaviour? More important, can anyone explain it?

 

(Dev 82.0.446.0 on W10 1909 18363.720)

10 Replies

  • uhhgio's avatar
    uhhgio
    Copper Contributor

    Noel Burgess This just started happeneing to me. I worried. Is it temporary? will it go away? I can't contact microsoft support due to it either. 

     

    • uhhgio 

      this specific problem seems to have something to do with cached data.

      try clearing cache and saved webpage files from here: edge://settings/clearBrowserData

       

       

  • A-Jahromi's avatar
    A-Jahromi
    Copper Contributor

    Noel Burgess 

    The request is blocked.

    {0Di6KXwAAAACGrl47YyiRT74i8t35AvjHQkwyRURHRTA4MTAAN2M0NTQ0NjEtNjE3NS00YjM1LWJmZDYtN2Y0NjM4YTNlYzdm}
    os windows 10 
    Microsoft Edge
    or
    google chrome
  • theAVLien's avatar
    theAVLien
    Copper Contributor
    Getting the same on a link to GPT/bootloader info. So it's not just windows server info. Microsoft has had a habit of moving things and
      • Noel Burgess's avatar
        Noel Burgess
        Steel Contributor

        HotCakeX 


        ... that link is probably pointing to a  script whose developer moved it ...

        That's probably the case, but I would normally expect to see an HTTP 404 'not found' response, not a snarky 'we think you're a bot, so we're not going to help you.'

         

        There's some reason why the MSFT server involved chooses to block what appears to be a legitimate request from Edge, rather than simply telling Edge that the requested resource isn't available. 

  • Same here on Version 82.0.458.0 (Official build) canary (64-bit)

    and on Firefox nightly 76a, so definitely Not Edge related issue

Resources