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

OctopusDeploy: LetsEncrypt challenge gets 303 redirected to https #3659

Closed
stopthatastronaut opened this issue Jul 12, 2017 · 2 comments
Closed
Assignees
Labels
area/infrastructure kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@stopthatastronaut
Copy link

According to the code, the /.well-known/acme-challenge/ path shouldn't trigger a redirect, but it does:

C:> $resp = iwr http://[testoctopus]/.well-known/acme-challenge/HiwUTK_5JF6QoMKP9veuwawTKJveHBNZpWtEeLSTnjQ -MaximumRedirection 0
C:> $resp.headers

Key Value


Transfer-Encoding chunked
X-UA-Compatible IE=edge
X-XSS-Protection 1; mode=block
X-Frame-Options DENY
X-Content-Type-Options nosniff
Referrer-Policy no-referrer
Content-Security-Policy default-src 'none'; connect-src 'self'; font-src 'self'; img-src data: https://www.gravatar....
Cache-Control private no-cache, no-store
Content-Type text/html
Date Mon, 10 Jul 2017 02:21:43 GMT
Expires Sun, 09 Jul 2017 02:21:43 GMT
Location https://[testoctopus]/.well-known/acme-challenge/HiwUTK_5JF6QoMKP9veuwawTKJveHBNZpWtEeLS...
Server Octopus Deploy/ Microsoft-HTTPAPI/2.0

@matt-richardson matt-richardson self-assigned this Jul 12, 2017
@matt-richardson matt-richardson added the kind/bug This issue represents a verified problem we are committed to solving label Jul 12, 2017
@octoreleasebot octoreleasebot added this to the 3.15.6 milestone Jul 13, 2017
@octoreleasebot
Copy link

Release Note: Handle Let's Encrypt http challenge when ForceSSL is enabled and https is configured on a custom port

@lock
Copy link

lock bot commented Nov 24, 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 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/infrastructure kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants