nextcloud / nextcloud/notify_push
Apache proxy configuration within Location directives with upgrade=websocket
Open
Nobody has claimed this yet.
documentation
enhancement
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
The Apache documentation could potentially be updated for Websocket Upgrade (2.4.47 and later), also I have found that using Location (note the Overlapping Webspace documentation) seems to work best, for example:
<Location "/push/">
<IfModule proxy_module>
ProxyPass "http://127.0.0.1:7867/"
ProxyPassReverse "http://127.0.0.1:7867/"
</IfModule>
</Location>
<Location "/push/ws">
<IfModule proxy_module>
ProxyPass "ws://127.0.0.1:7867/ws" upgrade=websocket
</IfModule>
</Location>
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 with the linked Apache mod_proxy WebSocket, Location, and overlapping webspace documentation, then inspect this repository’s existing Apache or deployment documentation if present. Compare the current guidance with the supplied Location example and document the upgrade=websocket configuration for Apache 2.4.47 and later. Done means the relevant setup guidance includes a clear working example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100