For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

jmanya_44531's avatar
jmanya_44531
Icon for Nimbostratus rankNimbostratus
Jun 08, 2014

iRule with iFile to show a maintenance page has crashed my APP

Hello friends,

Please, hope you could help me this time again.

I deployed an iRule to show a simple .jpg image containing a website maintenance message. The iRule is as follows:

when HTTP_REQUEST {
    if { [active_members pool_http] < 1 } {

    set ifileContent [ifile get maintenancepagelist1]
    HTTP::respond 200 content  $ifileContent 
    unset ifileContent

    }
    }

Once my web page was ready again (after maintenance), I performed a rollback by deleting the iRule. Unfortunately, the .jpg image survived and now it is in a place in my web page. It seems like the main portion of the app is served by the web server and the F5 adds the .jpg image. I have disable/enable the virtual servers, but I have not succeded.

Could you give some suggestion in order to troubleshoot this?

Thanks in advance

Jorge

application delivery
devops
iRules
LTM
management

3 Replies

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Jun 08, 2014

    Unfortunately, the .jpg image survived and now it is in a place in my web page.

    it is not from browser's cache, is it?

    have you tried to delete existing connection?

     tmsh delete sys connection cs-server-addr x.x.x.x cs-server-port yyy

x.x.x.x is virtual server ip
yyy is virtual server port
  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus
    Jun 09, 2014

    The image might have been cached by your browser or an intermediate caching proxy server you use. You should set "no-cache" and expiration time when setting up a temporary page.

     

  • Arie's avatar
    Arie
    Icon for Altostratus rankAltostratus
    Jun 09, 2014

    You used HTTP status code 200, which is defined as "OK" and is allowed to be cached. It can also wreak havoc on SEO.

     

    You won't be able to affect the clients (or proxies) that have already cached the item until the cache expires.

     

    For future maintenance pages you'll want to use HTTP status code 503 (Service Unavailable).