[JDEV] Help on Firewall

[Dave]

Fair enough, then ask your favorite Jabber server's firewall admin to
redirect port 443 to 5222.  (I tend to like that solution somewhat more
because it allows the server in question to continue to supply standard
HTTP service.)

 - Dave


Matthias Wimmer wrote:
> 
> Hi Dave!
> 
> Dave wrote:
> 
> >BTW - There's also another interesting solution, if your firewall's
> >blocked outgoing connections to port 5222 - convince the firewall admin
> >of your favorite Jabber server to redirect some other port (such as 80,
> >if web service isn't being needed - since blocking outgoing access to that
> >port selectively isn't too easy for a firewall admin if his users are
> >smart) to 5222, so when you connect to your.favorite.jabber.server:80,
> >you're actually connecting to the daemon on port 5222, the normal
> >Jabber server.  Sure, you can use HTTP polling if you prefer, but if
> >you don't need to, you'll appreciate all the advantages of a standard
> >TCP connection.  (This assumes that your firewall doesn't block all
> >outgoing TCP connections, of course.)
> >  
> >
> All company firewalls block port 80 or redirect them to the HTTP proxy. 
> It's better to bind the Jabber server to port 443. This port is normally 
> used for https and you can use a CONNECT over a HTTP proxy to connect to 
> this port. E.g. this is implemented in Gabber.
> 
> 
> Tot kijk
>     Matthias
> 
> -- 
> Fon: +49-700 77007770		http://matthias-wimmer.de/
> Fax: +49-89 312 88654		jabber://mawis@charente.de
> 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>