Forum Discussion

nbresto's avatar
nbresto
Icon for Nimbostratus rankNimbostratus
Dec 01, 2023

F5 LTM Vanity URL Rewrite

Hi all, Pretty new to F5 and have taken over management of a pair. I am having trouble updating some rewrite vanity urls. I need users to be able to put in the URL "example.com" and for the URL to ...
application delivery
Niels_van_Sluis's avatar
Niels_van_Sluis
Icon for MVP rankMVP
Dec 01, 2023

Try building the request and send it from the BIG-IP to the configured node(s) to see if you also get a status code of 404. Maybe you are requesting the wrong page. Below is an example with curl.

curl -v -k --resolve placeholder.com:443:<node_ip_address> https://placeholder.com/test/somepage.html

You can also add some extra debug logging to see what's actualy being send to the pool member. See: iRule to log HTTP Request and Response headers for specific client IPs (f5.com)

  • nbresto's avatar
    nbresto
    Icon for Nimbostratus rankNimbostratus
    Dec 05, 2023

    Hi Niels,

    Do I need a node set up for a rewrite to work? I'm able to http::redirect to the site (though the URL changes) so I figured I'd be able to rewrite as well or am I understand this wrong? 

    • Niels_van_Sluis's avatar
      Niels_van_Sluis
      Icon for MVP rankMVP
      Dec 05, 2023

      Hi nbresto,

      For a rewrite to work a node is needed. A redirect is something else. Does the client after a redirect, still makes a connection via the F5 BIG-IP? Did you try testing with curl?

      • nbresto's avatar
        nbresto
        Icon for Nimbostratus rankNimbostratus
        Dec 05, 2023

        Hi Niels,

         

        This is the output I got. Anything that looks bad here? I can see the http 200 response.


        C:\Users\nbresto>curl -v -k --resolve test.com:443:10.213.7.139 https://test.com/test

        * Added test.com:443:10.213.7.139 to DNS cache

        * Hostname test.com was found in DNS cache

        *   Trying 10.213.7.139:443...

        * Connected to test.com (10.213.7.139) port 443 (#0)

        * schannel: disabled automatic use of client certificate

        * ALPN: offers http/1.1

        * ALPN: server did not agree on a protocol. Uses default.

        * using HTTP/1.x

        > GET /test HTTP/1.1

        > Host: test.com

        > User-Agent: curl/8.0.1

        > Accept: */*

        > 

        < HTTP/1.1 200 OK

        < Content-Type: text/html

        < Last-Modified: Thu, 16 Nov 2023 06:23:24 GMT

        < Accept-Ranges: bytes

        < ETag: "016fd665518da1:0"

        < Server: Microsoft-IIS/10.0

        < X-Powered-By: ASP.NET

        < Strict-Transport-Security: max-age=31536000

        #<html> stuff </html>#

         

        * Connection #0 to host test.com left intact