adding examples and making modifications

[Rick-Anderson]

adding examples and making modifications

[tdykstra]

Several minor issues need fixing.

[tdykstra]

Suggested change

	Now when making request from browser:
	Now when making a request from browser:

[tdykstra]

Curly quotes (“”) should be changed to straight quotes (") throughout.

[tdykstra]

Suggested change

Each colored line (example highlighted) represents the lifetime of one request. The rule specifies two conditions as you can see. This means that any condition that gets met first then the denial will be applied. The rule will allow only up to two requests within 200 msec, and any further requests within this timeframe will be denied. As can be seen, the third request was triggered almost 20 msec after the first one, meaning now we have more than two requests within the 200 msec frame and hence the third one will be denied, and so will be the 4th and 5th and 6th.

Each colored line (example highlighted) represents the lifetime of one request. The rule specifies two conditions as you can see. This means that any condition that gets met first then the denial will be applied. The rule will allow only up to two requests within 200 msec, and any further requests within this timeframe will be denied. As can be seen, the third request was triggered almost 20 msec after the first one, meaning now we have more than two requests within the 200 msec frame and hence the third one will be denied, and so will the 4th and 5th and 6th.

[tdykstra]

Suggested change

	Http status code for denied requests in this example will be 403 and sub status code will be 502. This way you can tell the difference between normal Forbidden status code set by the application code and between the Forbidden set by the IIS IP Restrictions feature.
	Http status code for denied requests in this example will be 403 and sub status code will be 502. This way you can tell the difference between normal Forbidden status code set by the application code and the Forbidden set by the IIS IP Restrictions feature.

[tdykstra]

Suggested change

	Above codes are documented here: HTTP status code overview - Internet Information Services | Microsoft Learn
	The preceding codes are documented here: HTTP status code overview - Internet Information Services | Microsoft Learn

It looks like this should be a link.

[tdykstra]

Suggested change

	Now in case of “Enable Logging Only Mode” there will be no clients denied by this feature, meaning status code will be the expected result (normally 200 but it also depends on your application) and clients will receive the expected normal response, however, substatus code indicating that one of the two conditions was met will be logged in IIS logs. Below is an example:
	Now in the case of “Enable Logging Only Mode” there will be no clients denied by this feature, meaning the status code will be the expected result (normally 200 but it also depends on your application) and clients will receive the expected normal response, however, the substatus code indicating that one of the two conditions was met will be logged in IIS logs. Below is an example:

[tdykstra]

For guidance on what screenshots should look like, see https://review.learn.microsoft.com/en-us/help/contribute/contribute-how-to-create-screenshot?branch=main

In particular, red outline boxes are prescribed for calling attention to a part of the image, rather than yellow highlighting. I wouldn't reject the PR on that basis, but it's worth knowing about for any screenshots created or edited in the future.

[tdykstra]

It would be preferable to make the red arrow into the prescribed red outline box or a better arrow, and blackout using a rectangle rather than freeform hand-drawn black highlighting. image-3.png looks better in this respect, although to me it seems strange to call attention to a blacked out section of the screenshot.