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

Fail if customer is using Legacy IIS (IIS6) #1343

Merged
merged 3 commits into from
Sep 13, 2024
Merged

Fail if customer is using Legacy IIS (IIS6) #1343

merged 3 commits into from
Sep 13, 2024

Conversation

zentron
Copy link
Contributor

@zentron zentron commented Sep 12, 2024

LegacyIIS support was added many moon ago when IIS6 on Windows2003 was still supported however IIS7 on Windows 2008+ used different API.

As noted in the AutoDetect code the auto selection of this process only apples for Windows 2003 and below. Windows 2003 is no longer supported and so no customers should be relying on this code path.

Since the pending removal of this code path has never been warned, a temporary last-ditch support will be temporarily be supplied via an additional force variable.

Given the lack of support for servers that should be running IIS6, It is expected that this code will be removed within a few months.

@zentron zentron marked this pull request as ready for review September 12, 2024 20:44
Copy link
Contributor

@APErebus APErebus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just 1 question about a message

Comment on lines 65 to 68
throw new CommandException($"Support for IIS6 is no longer supported.\r\n"
+ $"Remove the {SpecialVariables.UseLegacyIisSupportForce} variable and ensure you are targeting IIS7+.\r\n"
+ $"To provide a temporary work around set the `{SpecialVariables.UseLegacyIisSupportForce}` to `true`.\r\n"
+ $"This capability will be very shortly removed without further warning.");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This doesn't make sense to me. We are telling them to remove the variable, but then tell them how to set the variable. Should we remove the 2nd line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah maybe bad wording. 🤔 ill give it a tweak.
Originally I just failed with no recourse, but decided to add the additional fallback. The phrasing probably got a bit muddled in that change.

@zentron zentron enabled auto-merge (squash) September 13, 2024 09:32
@zentron zentron merged commit aa13332 into main Sep 13, 2024
44 checks passed
@zentron zentron deleted the robe/no-iis6 branch September 13, 2024 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants