For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Mike_Rausch_628's avatar
Mike_Rausch_628
Icon for Nimbostratus rankNimbostratus
Aug 15, 2007

Proxy Pass

I was looking at an earlier entry about Proxy Pass and was wondering if it was what I needed to use.     I am having trouble with overseas clients not being able to connect to a socket server wh...
application delivery
dev
devops
iRules
Kirk_Bauer_1018's avatar
Kirk_Bauer_1018
Icon for Altostratus rankAltostratus
Aug 21, 2007
Your choices, in order from best solution but most difficult to OK solution but easier are:

 

 

1) Rewrite client/server to use native HTTP, HTTPS, or XML over HTTP protocol.

 

2) Rewrite client/server to encode existing protocol within HTTP or HTTPS.

 

3) Leave your protocol alone, but use port 443, and make sure your client reads the proxy settings from IE or gets them from the user and uses a "CONNECT servername" call to the proxy to open the pipe up to your server. You then send non-HTTPS traffic through this pipe and hope nobody notices.

 

 

Option 3 will work in a lot of cases but some proxies or firewalls will figure it out and block the traffic and/or in some cases close the connection and your client would have to handle re-connection.

 

 

The BIG-IP can't help with any of this, unfortunately.