Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 36653 invoked from network); 4 May 2009 19:44:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 May 2009 19:44:26 -0000 Received: (qmail 71536 invoked by uid 500); 4 May 2009 19:44:26 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 71470 invoked by uid 500); 4 May 2009 19:44:25 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 71460 invoked by uid 99); 4 May 2009 19:44:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 19:44:25 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [206.190.38.114] (HELO web50805.mail.re2.yahoo.com) (206.190.38.114) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 04 May 2009 19:44:14 +0000 Received: (qmail 44077 invoked by uid 60001); 4 May 2009 19:43:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rocketmail.com; s=s1024; t=1241466231; bh=4tijqgI8NltUKWwqeOsgVIg7XtfavOArBiNzRiUL9qQ=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=tTKbG0sCywKl6OTatn1M6nyKUD4BI+8PftAJTcHiaxIS+QJdK1S/AvzKrdoKwhGvSBICiRSZqkqV/Yg43G6IQfuv2PLrXoBn3JreaZo4rXK/lmA6GWagpndq5jZbwJ/jw9FaDZovl+FIHc3ZibUH60CEALp8DOIRiRkJdTGD4rk= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rocketmail.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=X90uDzlRnuxkfR52aooDQs5JhcVxWH9gBPRJtQk0misqnXUxyDKfny7EjxxZec228BEOWQzLxKjOlq9wpeLFTS9ACkOmBKUE/0aw+rB97suRR8Z4oWOJ4zDYE32eoCmVsQaBu43wuIhvEgrCp9UOI09GAZEcQNBDuZTALp/9tv4=; Message-ID: <493142.43019.qm@web50805.mail.re2.yahoo.com> X-YMail-OSG: okdhJFMVM1lW9k05Wj1dctl1w4T.QoJxhNfLLNlpbc9CsnLsyfnF0NiMQdq4Zv1Xtzd2YQVe_GYdbAjGuGb6.RUN55rbCaf7HUmvuaqVQ4AKaIg6wcNvb3nVG89Is2b3S43acIs1Y84T83jUA4rW.2bEBZlMjOPM5RsC1ZHzKKsIsSIl0bDbn_GgzMb6D_4D.bvFPwdoOqt_oxf_WySo_PnINqCkzSWBzECT3uL5rUjRySn79Gse_0SLipQlFPw4iIJAi9kSgGA0njJTJHw9lZC6.Nzp5jVY4O8QtdGdsM6wdMrF8LJ7Tkh86GEU_WM- Received: from [68.110.129.14] by web50805.mail.re2.yahoo.com via HTTP; Mon, 04 May 2009 12:43:51 PDT X-Mailer: YahooMailRC/1277.35 YahooMailWebService/0.7.289.1 References: <23374981.post@talk.nabble.com> Date: Mon, 4 May 2009 12:43:51 -0700 (PDT) From: Jose Luna Subject: Re: No way to use activeMQ via http. TCP works fine, but not http. Please help. To: users@activemq.apache.org In-Reply-To: <23374981.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org > 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.