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

Feature Request: Caddy--HTTP/2 web server with automatic HTTPS #1044

Closed
mervynsword opened this issue Dec 2, 2018 · 8 comments
Closed

Feature Request: Caddy--HTTP/2 web server with automatic HTTPS #1044

mervynsword opened this issue Dec 2, 2018 · 8 comments
Labels
feature Adding new functionality upstream Third party issue

Comments

@mervynsword
Copy link

Hi,you geniuses.

I have been using Caddy for a long time.It is a great web server,easy to use and with automatic HTTPS.

So can u guys add it into plugins?

The FreeBSD port is here:
https://www.freshports.org/www/caddy/

@fabianfrz
Copy link
Member

the nginx plugin can also serve content and supports HTTPS and HTTP/2.

You should give it a try (I has many features so expect big configuration forms).

@mervynsword
Copy link
Author

@fabianfrz
Yeah,I know,but caddy is much easier to config,and it can enable HTTPS by default and don`t need to think anything else.

@mimugmail
Copy link
Member

Are you sure it's worth it reinventing the wheel? Give it a try .. you'll master it too :)

@mimugmail
Copy link
Member

Just checked the Website, it's only free for private usage. No idea if this makes problems with integration

@fabianfrz
Copy link
Member

@mimugmail It seems to have a nice feature: TLS tamper (MITM) detection. The rest should be possible in nginx as well. If we really need it, I could write a C extension for it but such a feature would probably lock out enterprise users because it is quite common to intercept HTTPS for AV scanning.

@fabianfrz fabianfrz added the feature Adding new functionality label Dec 2, 2018
@fabianfrz
Copy link
Member

@mimugmail I created a ticket in the nginx bug tracker:
https://trac.nginx.org/nginx/ticket/1690#ticket

@fabianfrz
Copy link
Member

@fichtner @mimugmail @mervynsword Should we close this one, since all features should be in the nginx and the acme.sh plugin now?

@fichtner
Copy link
Member

I think in haproxy is HTTP/2 now too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Adding new functionality upstream Third party issue
Development

No branches or pull requests

4 participants