Forum Discussion
NimbostratusF5 LTM Vanity URL Rewrite
NimbostratusHi 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?
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
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
- nbresto
Also I am now seeing this image instead of "404 not found" when I involve the node with either an iRule or a policy.
