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.

Sign up for GitHub

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

Jump to bottom

IIS deployment doesn't configure HTTPS bindings correctly since 3.2.3 #2151

Closed
zentron opened this issue Nov 17, 2015 · 2 comments
Closed

IIS deployment doesn't configure HTTPS bindings correctly since 3.2.3 #2151

zentron opened this issue Nov 17, 2015 · 2 comments
Assignees
@zentron
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone
3.2.4

Comments

@zentron
Copy link

zentron commented Nov 17, 2015

If the user upgrades to 3.2.3 and performs an IIS deployment with certificates for the first time using a deployment plan generated in a previous version, the new binding format causes an error to be thrown.

Temporary quick work around is to go to the project step and edit the binding information to force it to save with the new format.
@zentron zentron added this to the 3.2.4 milestone Nov 17, 2015
@zentron zentron changed the title Backwards incompatable bug introduced in 3.2.3 surrounding IIS deployment of certificates Resolved: Backwards incompatable bug introduced in 3.2.3 surrounding IIS deployment of certificates Nov 17, 2015
@zentron zentron added the kind/bug This issue represents a verified problem we are committed to solving label Nov 17, 2015
@michaelnoonan michaelnoonan changed the title Resolved: Backwards incompatable bug introduced in 3.2.3 surrounding IIS deployment of certificates IIS deployment doesn't configure HTTPS bindings correctly since 3.2.3 Nov 20, 2015
@michaelnoonan
Copy link
Contributor

Release Note: Fixed a backwards-compatibility bug affecting IIS HTTPS bindings and their Certificates.

@lock
Copy link

lock bot commented Nov 26, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@zentron zentron

Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Milestone
3.2.4
Development

No branches or pull requests
2 participants
@michaelnoonan @zentron