Append https URL with 8443 port

Question

We have a Pool of servers listening on port 8443 for https for an application 7 the URL is accessed as https://www.abc.com:8443 now we want to host this site on f5 LTM with SSL offloading along with clientssl &amp; serverssl profiles.
In addition the users will access the site as https://www.abc.com poitiing to VIP but when request goes to Pool it should be https://www.abc.com:8443 hence port 8443 chould be added in http request.&nbsp;

nathe · Answer

TSP, by creating a VIP on port 443 and having pool members on port 8443, the BIG-IP will, by default for a standard virtual server, do port address translation automatically. You do not need the VIP to be on port 8443 or an irule to do this. &nbsp;
Hope this helps,&nbsp;
N&nbsp;

kai_wilke · Answer

Hi TSP,&nbsp;if you need to change the HOST-header value to match the non-443 port number of your pool members, you could use this code snippet...&nbsp;when HTTP_REQUEST_SEND { 
    clientside {
        HTTP::header replace "HOST" "[HTTP::header value HOST]:[LB::server port]"
    }
}Cheers, Kai&nbsp;

tsp_94471 · Answer

&nbsp;

raduioncu_16351 · Answer

It seems to me that all you need is to have the pool members on port 8443 (or 4443 as in the diagram?). There is no reason why this would not work.

Changing the host header to include :8443 would actually break the connection, since the browser does no consider the port part of the HOST.

nag_54823 · Answer

Hi TSP,

It could be ssl communication issue between LTM and pool members. Are you able to access your application directly bypassing LB ? does 3-way handshake and certificate exchange completed successfully on server side ?
openssl &amp; ssldump will be really helpful in this situation to clear out ssl communication issue.

Forum Discussion

Append https URL with 8443 port

8 Replies

AppWorld Berlin 2026 – iRules Contest Winning Results

One Quick Step to Make your website AI-Agent/MCP Ready with an iRule

IPv8 Would Fix My Routing Tables. It Will Never Ship.

Recent Discussions

Related Content

F5 HTTPS Redirect 2025

HTTP Multipart and Security Implications

The State Of HTTP/2 Full Proxy With F5 LTM

HTTP Request Smuggling Using Chunk Extensions (CVE-2025-55315)

HTTP To HTTPS Redirect 301

ABOUT DEVCENTRAL

RESOURCES

SUPPORT

PARTNERS