Re^2: HTTP::Proxy and Trillian

if your company's firewall does not allow outgoing connections to port 1863, putting an HTTP CONNECT proxy on your workstation will not help you, unfortunately.

If his own proxy to passes such connections through the company firewall, it should work.

Makeshifts last the longest.

Comment on Re^2: HTTP::Proxy and Trillian

Replies are listed 'Best First'.
Re^3: HTTP::Proxy and Trillian by robartes (Priest) on Oct 13, 2003 at 20:59 UTC
Correct, but judging by his description of the situation, that will not be the case. The FW blocks outgoing connections to said port - just putting a proxy on his workstation that does nothing but pass on the connection using HTTP CONNECTs will not make the least difference to the FW. To the FW, it's still an outgoing connection originating on the inside network. Or perhaps the company proxy he installed has a way to negotiate outgoing connections with the firewall, in which case your statement is of course correct. CU Robartes- who just occasionally tends towards the pedantic ;)	[reply]
Re^4: HTTP::Proxy and Trillian by Aristotle (Chancellor) on Oct 13, 2003 at 21:12 UTC
The OP explicitly mentioned that ~~Trillian~~ update { other messengers } works over his company proxy. Which is no surprise, as company proxies are usually used to to allow web traffic through the firewall: the firewall blocks all traffic other than eg traffic coming from a certain port range on the IP of the proxy. That way, talking to the proxy is the only way to reach the outside world. Makeshifts last the longest.	[reply]