Should websockets be enabled by default?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 222
- Forks
- 105
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 1
Description
It's had quite a lot of testing, and most of the clients (Python, Java) wil support it by the time 5.6 is released. Should we enable websockets (wss i.e. "secure" only) by default in the server, and provide an east config option in the generated OMERO.web nginx config?
Note for Nginx to proxy wss OMERO will need a self signed certificate (or even better, an official certificate even though it won't be verified by clients) with a supported cipher i.e. not anon-DH as is currently used for omero ssl.
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 reviewing the server's websocket defaults and the generated OMERO.web nginx configuration, then check the stated Python and Java client support and the certificate and cipher requirements for wss. Done would require a documented decision on whether secure websockets are enabled by default and how users configure the nginx proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, nginx, python
- Domain
- backend, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100