iRule to assign node based on URI, bypassing source IP persistence
Hello, We are using a standard VS to load balance HTTPS traffic to 2 web servers, using source IP persistence. For a particular statistics application we need to bypass load balancing and persistence and send the HTTPS traffic to the 2nd web server. I customized this iRule to catch the URI /stats/stats.js and send to a pool containing only the 2nd server : when HTTP_REQUEST { if { [string tolower [HTTP::uri]] starts_with "/stats/" } { pool stats.https.pool } else { pool website.https.pool } } The default condition seems to work fine as all URI's are working. But on the /stats/stats.js URI I get permanently 404's. According to a logging iRule I'm using I see that regular traffic is sent to either one or the other web servers, and the /stats/ traffic to the 2nd one only... But I still get 404's. Also CURL from the BIG-IP shows that the URL is accessible on the destination server. I tried to add 'persist none' before the pool assignment but that didn't help. Any advise would be strongly appreciated ! I'm sure this is a basic problem but I don't get it right now 🙂 Cheers, Gerald
404 redirect exception
Hi I hope someone can help with this I have a 404 redirect rule that checks on the primary pool first and if it cant find check in another location, if it cant find it on the second server it sends to a search results page on the primary pool via another irule. Works well, but the problem is the client gets a 200 from the search results so any page that is not found gets crawled. I want to be able to put a 404 on the search results page, so it wont be crawled, but would not be caught up in irule the loop. I have tried below it is getting caught up: when HTTP_REQUEST { set uri [string tolower [HTTP::path]] } when HTTP_RESPONSE { if { [HTTP::status] == 404 && $uri ne "/search-results/?p=nothere"} { HTTP::redirect "http://secondserver.location$uri" } } Has anyone been able to do this? Cheers Brettsend people to website 404 page for illegal URL block
We have a policy that is set to allow only existing URLs within it. My client would like people to receive a 404 "page not found" message and not an ASM response page when a user tries to access an illegal (nonexistent) URL. Any suggestions on how to achieve this? Thanks