Forum Discussion

Rameez_Ilyas_Qu's avatar
Rameez_Ilyas_Qu
Icon for Nimbostratus rankNimbostratus
Sep 11, 2019

URL Masking for a URL going back in HTTP Response

Hi,

 

My first ever post, i hope i don't sound like a stupid, i am a newbie so i will try my best to explain what i want to achieve. (Not a native English speaker so excuse my writing skills)

 

So i have an application hosted on the internet. I have made a Virtual server and applied a TRANSPARENT Security POLICY on the virtual server.

 

My public URL resolves to a Public IP and the page is opened over the internet. Everything is working fine. SSL certificate installed on F5.

 

The F5 translates the hit to HTTP server and fetches the page back. Now the problem : It is displaying a secured internal port over the internet.

 

User is Opening www.securebankingexample.com .. and when page is returned back to the user , browser is showing www.notsecurebankingexample.com:8888.

 

Can i mask the www.notsecurebankingexample.com:8888 with www.notsecurebankingexample.com:xxxx

 

I tried to write an IRule for HTTP response and attached it to Virtual server.

 

Is this going to work ? Can F5 mask a URL which is coming from HTTP server below. I just need to hide the port or display something on customer browser.

 

I am sorry if this sounds stupid :(

 

 

2 Replies

  • HI Rameez,

    I don't think it is possible to mask a non standard port number as in URL, it's part of the host name and not the URI. From your description it's not clear where both www.securebankingexample.com and  www.notsecurebankingexample.com have public DNS record and where they are using same public IP. If I was trying to make www.notsecurebankingexample.com publicly available over standard HTTPS port , which is available internally over HTTPS on port 8888, I would give it new standard HTTPS virtual server with new public IP and forward traffic to the internal VIP either using an iRule or LTM policy.

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    Try the following to see if it solves it all:

     

    • In your HTTP profile add "X-Forwarded-Proto: https" to the field "Request Header Insert";
    • In your HTTP profile, enable "Redirect Rewrite" with "Matching" or "All".

    Also see Profiles for Managing HTTP Traffic.