playframework / playframework/playframework
Enable HTTPS and HTTP/2 by default
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 12.6k
- Forks
- 4k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 29
Description
Something to consider for the next release of Play. By enabling HTTPS and HTTP/2 by default we make it easier for users to use these more modern protocols.
Things to consider:
- how to find the Jetty ALPN agent (or just expect Java 9+)
- how to make the server certificate information available for testing
- how to make the server certificate information to the running application (e.g. so the application can connect to itself)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how Play currently configures its server and how Jetty ALPN or Java 9+ support could enable HTTPS and HTTP/2 by default. Determine how certificate information should be exposed to tests and to the running application; done means the default server supports both protocols and those certificate details are available in both contexts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100