Hello, I have been experimenting with the various transport layers and I'm happy how they perform quite well. Going a bit further with the transports and connectivity on disparate networks and their various policies, we have a definite need to tunnel our protocol via HTTP/HTTPS to get around firewall issues on the client side. Some clients are forced to access outside services on port 80/443 using their in-house HTTP proxies such as squid, etc.. Using the HTTP/HTTPS transport in ActiveMQ performs very well when a direct connection to the ActiveMQ server is available, however we noticed that some HTTP proxy server configurations cause tremendous issues on the communications.
To understand our application in a bit more detail, our app is basically a chat protocol with the server active as a hub - similar to IRC. The protocol is real-time and the messages should be delivered in a timely manner. Our test scenario has squid configured as its default configuration and our ActiveMQ HTTP clients are connecting using the following URI: http://some.remote.host:80?proxyHost=192.168.30.15&proxyPort=8080 If anyone has any ideas as to how to attain good connectivity via HTTP proxies, I would be very interested in hearing them. Thanks in advance -- View this message in context: http://www.nabble.com/HTTP-HTTPS-transport-via-HTTP-proxy%3A-squid-et-al.-WRT-firewalls-tf4246688s2354.html#a12085375 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
