Cert invalid for ThePollyProject.org

App-vNext / Polly

Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+.

https://www.thepollyproject.org

BSD 3-Clause "New" or "Revised" License

13.42k stars 1.23k forks source link

Cert invalid for ThePollyProject.org #718

Closed SeanKilleen closed 7 months ago

SeanKilleen commented 5 years ago

Summary:

Was looking into converting some http URLs to https in the MS docs.

When navigating to https://thepollyproject.org/ ....

Expected behavior:

Site loads with https

Actual behaviour:

Looks like the cert is only set up to cover https://thepollyproject.azurewebsites.net/

If this project is a .NET Foundation project, I believe you are eligible for a free SSL cert for your domain:

We've partnered with DigiCert to provide SSL certificates for the .NET Foundation OU. We set your project up in Digicert's system, you request the certificate for your website, and they're paid for centrally by the foundation.

Or, since you're on the azure app service, if you're willing to spend a few bucks, the setup for an SSL cert there isn't too tough. I've done it before; let me know if I can be of help.

Wanted to drop this here in case it's useful; feel free to close if not. Thanks!

joelhulen commented 5 years ago

Thanks for the heads-up!

I've been thinking about changing up this site anyway to be statically hosted and served up for free using GitHub or similar. Then just accept PRs to update the site content. I think this might be a good excuse to get in there rework the site.

SeanKilleen commented 5 years ago

👍 If you're interested in help on the conversion, feel free to create a repo and grant me push access; I currently run my site on GitHub pages via Jekyll and I think we could do a 1:1 conversion reasonably quickly.

joelhulen commented 5 years ago

Thanks. We're using ghost for the blog so I'm not sure what the upgrade path is.

SeanKilleen commented 5 years ago

Likely something along the lines of:

Get basic Jekyll up & running and deployed on GitHub pages
If you find a Jekyll theme that gets pretty close to your current layout, that'd probably be the easiest because then a lot of minutiae is handled by updating a _config.yml file.
Otherwise, get the CSS, JS, etc. going with a few test pages & posts
Import the rest of the posts with https://import.jekyllrb.com/docs/ghost/
Get the author profiles set up if you're still trying to link to them
Check the SEO, redirects, etc. (jekyll has plugins that help with this)
Add a CNAME file in the root of the repo
Change your registrar to point to GitHub pages
Get set up with a Netlify account (fantastic build & preview functionality for PRs)
Set up Netlify CMS (free library, integrates with GH pages, allows CMS-like feel of Ghost)

If you want to throw CloudFlare in front of it while you're at it, I've got an older post on those steps.

304NotModified commented 3 years ago

Any news on this? Plain http is a bit strange nowadays. I really like to see https everywhere

SimonCropp commented 1 year ago

@SeanKilleen this seems to be fixed?

SeanKilleen commented 1 year ago

Looks like it! This can be closed.

martincostello commented 9 months ago

Looks like it expired again @joelhulen.

Specifically, the non-www.

/cc @scottthurlow

github-actions[bot] commented 7 months ago

This issue is stale because it has been open for 60 days with no activity. It will be automatically closed in 14 days if no further updates are made.

SeanKilleen commented 7 months ago

Bumping just because I assume someone still wants to see it and get it fixed 👍

joelhulen commented 7 months ago

I realized that I only had SSL binding set up for www.thepollyproject.org and not thepollyproject.org. It is now resolved. Thanks for bringing this back up!