Update backend.loc / Websocket reverse proxy management - #96
Open
mngoe wants to merge 1 commit into
Open
Conversation
|
delcroip
approved these changes
Mar 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Description
This PR adds WebSocket support to the nginx reverse proxy configuration for the backend API location.
The nginx proxy configuration has been updated to properly handle WebSocket connections by:
UpgradeandConnectionheaders for WebSocket negotiationThis enables real-time bidirectional communication between the frontend and backend, which is essential for features requiring instant updates without polling (e.g., notifications, live data feeds, video stream management, Claim AI module).
Type of Change
Related Issue(s) / Task(s)
Technical Details
Modified file:
openimis-dist_dkr/conf/nginx/locations/backend.locChanges made:
proxy_http_version 1.1;- WebSocket requires HTTP/1.1proxy_set_header Upgrade $http_upgrade;- Forwards upgrade headerproxy_set_header Connection "upgrade";- Sets connection upgrade modeproxy_read_timeout 86400;- 24-hour timeout for persistent connectionsTesting
After deployment, WebSocket connections can be tested by:
nginx -tnginx -s reloadDemo
N/A - Infrastructure configuration change
Checklist