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

HTTP2 support in Apache #3647

Closed
bmw opened this issue Oct 17, 2016 · 7 comments
Closed

HTTP2 support in Apache #3647

bmw opened this issue Oct 17, 2016 · 7 comments
Labels
area: apache feature request needs-update priority: significant Issues with higher than average priority that do not need to be in the current milestone.
Milestone

Comments

@bmw
Copy link
Member

bmw commented Oct 17, 2016

The Apache version of #3646.

@stale
Copy link

stale bot commented Jun 14, 2019

We've made a lot of changes to Certbot since this issue was opened. If you still have this issue with an up-to-date version of Certbot, can you please add a comment letting us know? This helps us to better see what issues are still affecting our users. If there is no further activity, this issue will be automatically closed.

@stale stale bot added the needs-update label Jun 14, 2019
@bmw
Copy link
Member Author

bmw commented Jun 14, 2019

While I've seen way more requests for this in Nginx than Apache, I think this is probably still something we should do. As of writing this, the proposed changes to Mozilla's SSL config generator tell you to enable HTTP2.

@stale stale bot removed the needs-update label Jun 14, 2019
@stale
Copy link

stale bot commented Jun 13, 2020

We've made a lot of changes to Certbot since this issue was opened. If you still have this issue with an up-to-date version of Certbot, can you please add a comment letting us know? This helps us to better see what issues are still affecting our users. If there is no activity in the next 30 days, this issue will be automatically closed.

@stale stale bot added the needs-update label Jun 13, 2020
@bmw bmw removed the needs-update label Jun 15, 2020
@bmw bmw added the priority: significant Issues with higher than average priority that do not need to be in the current milestone. label Oct 8, 2020
@github-actions
Copy link

We've made a lot of changes to Certbot since this issue was opened. If you still have this issue with an up-to-date version of Certbot, can you please add a comment letting us know? This helps us to better see what issues are still affecting our users. If there is no activity in the next 30 days, this issue will be automatically closed.

@bmw bmw closed this as not planned Won't fix, can't repro, duplicate, stale Jun 16, 2023
@osirisinferi
Copy link
Collaborator

@bmw I'm curious why this issue with priority significant is being closed? 🙂 To me it still sounds like a good idea.

@bmw
Copy link
Member Author

bmw commented Jun 21, 2023

It's something we haven't gotten to and/or prioritized in almost 7 years and it seems unlikely to happen to me especially when there doesn't seem to be significant user demand for it. With that said, if you think this issue is especially important, you're welcome to reopen it with your GitHub powers.

@osirisinferi
Copy link
Collaborator

especially when there doesn't seem to be significant user demand for it.

That's a good point. I guess most novice users won't care (ignorance is bliss) and advanced users will know how to enable it manually. Let's keep it closed unless someone actively asks for it 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: apache feature request needs-update priority: significant Issues with higher than average priority that do not need to be in the current milestone.
Development

No branches or pull requests

2 participants