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

Dennis_Andrade_'s avatar
Dennis_Andrade_
Icon for Nimbostratus rankNimbostratus
Feb 18, 2014

HTTP profile: x-forwarded-proto

I have a virtual server configured on a custom port 8080 with a client SSL profile attached to it. So the user will enter https://hostname.com:8080 to access the virtual server. So far so good. I hav...
application delivery
availability
design
LTM
Dennis_Andrade_'s avatar
Dennis_Andrade_
Icon for Nimbostratus rankNimbostratus
Feb 18, 2014

Option 2 is the best one to go with but I'm little confused on the STREAM profile. Let's say my public URL for the users to access the VIP is https://publichost.com:8080 Then after the user login they are taken to the backend server pool but it fails because it removed the port number: https://publichost.com/backendURI/

 

In the STREAM profile I added the following to the "target" field (did not use iRule):

 

@https://publichost.com@https://publichost.com:8080@

 

Accessing that URL after the change I'm able to login but getting to the backend server gives me an error message right away: The server did not return a response for this request. Not sure I setup the STREAM profile correctly