Ask Slashdot: Why is Microsoft Blocking Its Own Server Pages?

Long-time Slashdot reader lpq writes: I followed a link that pointed at a Microsoft security advisory about “.lnk” files. The original link, https://www.microsoft.com/en-us/technet/security/advisory/2286198.mspx, produced this message:

Your request has been blocked. This may be due to several reasons.
1. You are using a proxy that is known to send automated requests to Microsoft. Check with your network administrator if there is any proxy and what User-Agent they are sending in the request header.

2. Your request pattern matches an automated process. To eliminate, reduce the volume of requests over a period of time.

3. Reference ID: 41.70790b91.4823110533.409105b4

It turns out the advisory number doesn’t matter, just the extension for “Active Microsoft Server Page” (https…/.mspx) at the end. I guess there were too many security advisory lookups for MS to handle! *snort*!

The .mspx extension indicates a page using a special internal Microsoft rendering framework with a custom web handler (built in ASP.Net). But I ran some tests Saturday, and observed the exact same glitch described above using three different browsers — Firefox, Edge, and Brave. Anyone have a theory about what’s going on?

Leave your thoughts in the comments. Why is Microsoft blocking its own server pages?

Read more of this story at Slashdot.

Source: Slashdot