Hey Hiroaki :) It doesn't use http proxies, but Paul Curtis's recently released Jabber External Transport (JET ==> http://jabber.terrapin.com/jsp/wiki.jsp?JET) is able to pierce firewalls. It's a set of two very simple components, and it's still in the alpha/beta stage of development, but it (reportedly) works quite well.
-- James Hiroaki Nakamura wrote: > Hi, > I am trying to let a jabber client make a connection via a http proxy. > Also I would like messages to be protected by SSL. > > I found there are two options out there. > > - "HTTP proxy passthrough" > http://oid.jabber.org/?oid=971&all=1 > - JEP-0025 > http://www.jabber.org/jeps/jep-0025.html > > I think the former is simpler, also preferrable since no extra port > for http is needed. You just need the port for jabber protocol (with > the support for ignoring HTTP PUT headers, which was implemented in > jabberd-1.4.1). > > I have three questions about these specs. > > Q1) What status are these two specs in? Which to pick one? Or keep > these two and let users select one when they run clients? > > Q2) I also ask that this is possible with the former spec when a proxy > allows a https connection with the port number other than 443? > 1.client -"connect jabber.org:5223"-> HTTP proxy > 2.proxy --> jabber.org:5223 > > If it is possible, I think this is the simplest. > > Q3) In JEP-0025, why POST request contents are not URL-encoded? > I think is is no problem if they are URL-encoded and also think > they should be. Is there a reason for that they are not? > > -- > )Hiroaki Nakamura) [EMAIL PROTECTED] -- James Widman jabber:[EMAIL PROTECTED] For Loops: part of a balanced NP-complete breakfast. _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
