Does iRule support any port define for HTTP and HTTPS?

Which port are you trying to insert into the header? the client port, or the virtual server port?

Users enter http://website.com:18100 but it needs to be redirect to https://website.com:18100

HTTPS:18100 is the setting on F5 login url is https://website.com:18100 web server behinds are listening on http/https 18100/18101

That should not be a problem. on your HTTP vs your irule would be when HTTP_REQUEST { HTTP::redirect "; }

On the HTTPS virtual (once traffic is redirected to it), are you trying to pass the cient IP to the server in a header? If so, the rule you have listed will do that.

when HTTP_REQUEST { HTTP::header insert WL-Proxy-Client-IP [getfield [IP::client_addr] "%" 1] }

yes we want to pass Client IP to the server. so the real IP will be captured on the PeopleSoft.

HTTP_REQUEST { HTTP::redirect ";; }

HTTP_REQUEST { HTTP::header insert WL-Proxy-Client-IP [getfield [IP::client_addr] "%" 1] }

Do we combine 2 lines of code? Or they are setup on different places?

Are the servers providing the redirect to https://website.com:18100? Or are you wanting to do it on the F5?

If you are doing it on the f5: 1. create your http virtual on port 18100 2. add an irule with "when HTTP_REQUEST { HTTP::redirect "; }" 3. create your https virtual on port 18101

if the server is providing the redirect to https:://website.com:18100, then we need to do something additional, particularly if the backend https servers are listening on 18101. 1. server sends redirect to https://website.com:18100 2. request is received at F5 on https virtual server. Host header value is website.com:18100. 3. need to rewrite the host name prior to sending to server on backend. So add an irule to https virtual with the following lines:

when HTTP_REQUEST { HTTP::header insert WL-Proxy-Client-IP [getfield [IP::client_addr] "%" 1]} when HTTP_REQUEST_SEND { HTTP::host website.com:18101 }

no there's no redirect on the web server behind F5. Yes I would like the F5 to redirect.

I will try your solution and get back to you.

Additionally, modify your redirect rule to not be static

when HTTP_REQUEST { HTTP::redirect "https://[HTTP::host][HTTP::uri]}

Does this work for SSL offloading?

Yes. In fact, decrypting the client side is required. Whether or not you reencrypt is just a matter of adding the server ssl profile and making sure you have the correct pool members