activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: No way to use activeMQ via http. TCP works fine, but not http. Please help.
Date Tue, 05 May 2009 09:41:01 GMT
Hi,

there's currently an effort to improve http transport for 5.3 release

https://issues.apache.org/activemq/browse/AMQ-2238

Please post all your comments there and I'll try to resolve them.

Cheers
--
Dejan Bosanac

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net

On Mon, May 4, 2009 at 9:43 PM, Jose Luna <j-luna@rocketmail.com> wrote:

>
>
> > Jose Luna-2 wrote:
> > >
> > > I don't have any recommendation regarding activemq and HTTP but you may
> > > consider tunneling openwire through SSL
> > > (http://activemq.apache.org/ssl-transport-reference.html).    If you
> set
> > > your broker up to use port 443, proxies won't be able to distinguish
> > > between this traffic and HTTPS, so the traffic will be allowed to pass
> > > through.   Actually, you would be able to get away with running the
> > > traffic over port 443 without using the SSL transport, but that somehow
> > > seems more deceptive ;) .   For more info, see
> > > http://tools.ietf.org/html/draft-luotonen-web-proxy-tunneling-01 .
> > >
> > >
> > >
> > >
> > Thank you for your reply, sir.
> > Other words, you telling I may use 443 port via tcp. An my clients will
> be
> > able to connect to server through this port even if they under the proxy.
> > Correct?
> >
> > Any way, guys, could you provide me other solutions, please.
> >
> > Thank you.
>
>
> Yes.  It's just a suggestion that I thought you might find useful.  You
> will need to be able to do the HTTPS handshake (see the ietf.org link I
> sent in my previous email).  You will also need to be able handle proxy
> authentication for users that requrie it, but that's something you would
> have to handle anyway if you are dealing with proxies.
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message