Additional information needed for apps using SignalR/WebSocket

[AlbertoPa]

When Apache is used as proxy for apps relying on WebSocket:

• The mod_proxy_wstunnel module needs to be enabled
• The virtual host configuration needs to include additional settings to allow the WebSocket connection to be established. The example at the top of the page becomes something like:

<VirtualHost *:*>
    RequestHeader set "X-Forwarded-Proto" expr=%{REQUEST_SCHEME}
</VirtualHost>

<VirtualHost *:80>
    ProxyPreserveHost On
    ProxyPass / http://127.0.0.1:5000/
    ProxyPassReverse / http://127.0.0.1:5000/
    ServerName www.example.com
    ServerAlias *.example.com

    # Added block
    RewriteEngine On
    RewriteCond %{HTTP:Upgrade} =websocket [NC]
    RewriteRule /(.*)           ws://127.0.0.1:5000/$1 [P,L]
    RewriteCond %{HTTP:Upgrade} !=websocket [NC]
    RewriteRule /(.*)           http://127.0.0.1:5000/$1 [P,L]
    # End added block

    ErrorLog ${APACHE_LOG_DIR}helloapp-error.log
    CustomLog ${APACHE_LOG_DIR}helloapp-access.log common
</VirtualHost>

Thanks!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: cfd9a1f0-c1b6-4443-0700-4c5beafeed03
• Version Independent ID: c22ca7a0-d1d4-200d-fc36-a9798d350c6e
• Content: Host ASP.NET Core on Linux with Apache
• Content Source: aspnetcore/host-and-deploy/linux-apache.md
• Product: aspnet-core
• Technology: aspnetcore-hostdeploy
• GitHub Login: @guardrex
• Microsoft Alias: spboyer

[guardrex]

Thanks @AlbertoPa ... I'll mark this for the Product Unit (PU label) to take a look at for coverage. They'll either work it directly on the next engineering doc sweep or give me instructions on what to cover where. Thanks for opening the issue.

[donhuvy]

I have a hard time for deploying, this is my experience about this task https://stackoverflow.com/questions/58196221/asp-net-core-3-blazor-run-on-localhost-of-server-ok-but-run-outside-server-err