Kbase 21413: Connecting To A SonicMQ Broker Using A Reverse Proxy Server
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/10/2001 |
|
SUMMARY:
This Solution applies to SonicMQ version 3.x. It discusses how a client connects to a broker through a firewall using a reverse proxy server.
EXPLANATION:
A client application that needs to connect to a SonicMQ broker through a firewall using a reverse proxy, connects to the reverse proxy server (for example, http://localhost:80). The SonicMQ internal client code appends /SC to the URL that the client application used to connect to the reverse proxy server (http://localhost:80/SC), creating the URI that the proxy server needs. The proxy server recognizes this as a SonicMQ request, maps and forwards the request to a SonicMQ broker. The proxy server is able to map and forward this request because it has been configured to do this. How a proxy server is configured to map and forward the request depends on the proxy server being used. To find more information about supported proxy servers, review the SonicMQ Release Notes.
Here is an example of what you might have for an Apache Configuration:
ProxyPass /SC http://serverhost:2506/SC
ProxyPassReverse /SC http://serverhost:2506/SC
References to Written Documentation:
SonicMQ 3.x Deployment Guide, "Security," "Using a Server-side Reverse Proxy"