Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix IIS config sample by changing from HTML to XML #1050

Merged
merged 1 commit into from Apr 23, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -211,7 +211,7 @@ This example shows how to unlock the section. Since it is locked at the applicat

There are cases where it is useful to unlock sections for a specific path only and to keep them locked for all other paths. The following example builds atop the previous one, and shows how to unlock the section for two specific sites only; for all other sites it will remain locked.

[!code-html[Main](deep-dive-into-iis-configuration-with-iis-7-and-iis-8/samples/sample8.html)]
[!code-xml[Main](deep-dive-into-iis-configuration-with-iis-7-and-iis-8/samples/sample8.xml)]

For each "exception" path that needs unlocking, there needs to be a different location tag.

Expand Down
Expand Up @@ -4,7 +4,7 @@
</system.webServer>
</location>

<location path="TrustedSiteTwo" overrideMode="Allow"><span style="font-family:Calibri; font-size:11pt">
<location path="TrustedSiteTwo" overrideMode="Allow">
<system.webServer>
<modules/>
</system.webServer>
Expand Down