irule maintanance page issue
Can anyone out there tell me what could be wrong with this code for an irule to reference HTML for a maintance splash page? when HTTP_REQUEST { if { [active_members [LB::server pool]] == 0 } { check if client access from internal subnet if { [IP::addr [IP::client_addr]/8 equals 10.0.0.0] } { pool alternate_pool } else { HTTP::respond 200 content { Sorry Page Sorry, The website is not available. Please try again later } } } I am losing my mind over trying to figure it out. it is giving me a missing bracket error and when I input it into notepad++ it isn't showing any error. here is the errors it is giving me 01070151:3: Rule [/Common/test_maintanance] error: /Common/test_maintanance:1: error: [parse error: missing close-brace][{ if { [active_members [LB::server pool]] == 0 } { check if client access from internal subnet if { [IP::addr [IP::client_addr]/8 equals 10.0.0.0] } { pool alternate_pool } else { HTTP::respond 200 content { Sorry Page Sorry, The website is not available. Please try again later } } }] /Common/test_maintanance:2: error: [command is not valid in the current scope][if { [active_members [LB::server pool]] == 0 } { check if client access from internal subnet if { [IP::addr [IP::client_addr]/8 equals 10.0.0.0] } { pool alternate_pool } else { HTTP::respond 200 content { Sorry Page Sorry, The website is not available. Please try again later } }
Best approach to serve maintenance page
Hi, We need to put website under maintenance for about 6 hours. Traffic flow: Clients -->Akamai--->F5-->Backend servers. We have maintenance page hosted in AWS cloud Front. which approach is better? DNS Change – Temporarily point our domain (via CNAME) to CloudFront by adjusting the TTL to 2 minutes. F5 Configuration – Issue a 302 redirect from F5 to CloudFront or forward (reverse proxy) traffic from F5 to CloudFront by modifying the Host header. This keeps the browser on our domain and returns a 200 OK. Main concerns : Avoiding browser/edge caching issues (we can clear Akamai cache if needed). Ensuring a quick rollback after maintenance. Which approach would be best? Could you advise on the correct implementation?