microsoft / iis.common

Common source and libraries used by IIS projects

Microsoft IIS Common

The repository contains common resources shared by IIS Out-Of-Band (OOB) products.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

iis.common's Issues

Intercept or inspect pre-normalized path

Hi folks,

I was hoping someone with a reasonable familiarity with IIS's inner workings could take a look at this question on Stack Overflow. I'm having trouble understanding where path normalization (the function that follows these lines, maybe?) occurs in the request life-cycle, and whether I can operate at any level on the pre-normalized path without doing something wildly inadvisable.

Thank you.

Add mof2trace to iiscommon as a prebuilt binary.

This repo is missing important files

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Visual C++ tools from Nuget

Currently we are using a NuGet package to get Visual C++ tools and compilers to get “consistent” builds. Although at some point this approach may have helped us, currently it has some drawbacks:

1. This is not supported. The owner of the NuGet package has delisted the package. The blog post about Visual C++ tools on NuGet has also been removed. There’s no replacement for it. We can use it because we know the exact version and name.
2. The specific compiler version we use causes a compiler warning.
3. The specific compiler version might have security issues we may never know. C++ tools and compilers get better every day with security improvements but we can’t take advantage of this.

In our CI and official builds, we use Hosted VS 2017 build machines. They will have the standard toolset we should be using. Since we test our products before release, I don’t see the drawback of using the latest compilers before releasing a new version of the product. I also don’t see the appeal of using a consistent compiler for each release. I suggest we remove this step from our Common build steps.

IIS ssl cert bindings are not getting updated

I am using azure vmkeyvault extention to poll for cert update in keyvault. Once a new certificate is published I get that certificate in my machines' My store. After some time when I browse for https://localhost I get the thumbprint of new certificate. But when I check IIS bindings I still see the old certificate binded with https. I tried netsh to check the binding but it gives me old cert thumbprint. But Client is recieving new updated certificate. The CName of both the certificate is same.

IIS 7.5 Change .NET Framework Version setting under Actions Manager Server

Environment:
IIS version 7.5
OS version windows server 2008 R2

Steps Followed:
Open IIS Manager.
On the Connections pane,select server node.
On the Action pane select change .net framework version and select version 4.0 and save chnages.

After reopen IIS manager console changes revert and does not save it.

Windows Server 2019: Built-in SMTP server

Environment:
OS:Windows Server 2019
IIS:IIS 6

Bug in Windows Server 2019
Mail will not be sent correctly if the SMTP service start-up type is set to "Automatic" (i.e. start immediately on boot). If the SMTP service is set to manual start and then started manually from either services.msc or from IIS6 manager, e-mail will leave the queue and get delivered to the recipients.

If "Automatic" start-up is used for the service, any attempts to send e-mail will always result in the e-mail getting stuck in the queue and the event 4006 (see initial post above for details) getting written to the event log.

Step-by-step to reproduce the issue:

Install SMTP server feature
Go to IIS6 manager, right-click SMTP virtual server and click "Properties"
Go to the "Access" tab
Click "Connection...", select "Only the list below" and add 127.0.0.1. Click "OK".
Click "Relay...", select "Only the list below" and add 127.0.0.1. Uncheck the checkbox at the bottom of the window. Click "OK".
Click "OK" again to exit the SMTP virtual server properties.
Open services.msc and set the "Simple Mail Transfer Protocol (SMTP)" service startup type to "Automatic"
Reboot the computer and attempt to send e-mail

A work-around is to set the start-up type to "Automatic (Delayed Start)". This will, if I am correctly informed, result in the SMTP service getting started 2 minutes after the last "Automatic" service has been started. This is not an optimal solution, but it'll do for the time being.

Manually Rotating in IIS

For iis log module,automatically rotate is not enough, customer also wants manual rotate right which means customer wants to set a trigger for iis to create logs whenver he wants.

Investigate checking-in Azure DevOps build definitions into IIS.Common

Enable CFG and Spectre mitigations for all IIS projects

MinimalRebuild is deprecated.

Remove it from debug.props.

The temporarily added hard-coded version 1.1.282 for the signing plugin should be removed

We added "version: 1.1.282" as a workaround way of the problem of the latest build. When the issue is fixed, we should roll back the change.