nextcloud / nextcloud/nextcloudpi
Option to disable HTTP2 when behind external proxy
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Description
An option to disable HTTP2 (h2,h2c) from GUI would be desirable and its use should be advised if nextcloudpi is placed behind a reverse proxy.
HTTP2 causes issues when nextcloudpi is behind a NGINX reverse proxy because nextcloudpi will return "Upgrade: h2,h2c" header for every request. This will cause mobile Safari clients to fail to connect to Nextcloudpi altogether. On the other hand, if the upgrade header is removed, notify_push websocket connection will no longer work since in this instance the "Upgrade: websocket" header will be removed.
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 locating the GUI option handling and the HTTP/2 and reverse-proxy configuration for NextcloudPi. Check how NGINX and notify_push websocket headers are currently handled, then define the disabled-HTTP/2 behavior and verify that websocket connections still work behind an external proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100