Forum Discussion

Matt_Breedlove_'s avatar
Matt_Breedlove_
Icon for Nimbostratus rankNimbostratus
Aug 01, 2011

Nullifying a particular GET request inside a TCP connection

Situation is a single tcp connection from one client to one server using a VS. Client makes multiple GET requests to the VS using the same tcp connection.     One of those GET requests I would ...
application delivery
dev
devops
iRules
  • Kevin_Davies_40's avatar
    Kevin_Davies_40
    Aug 02, 2011
    Its all in the details.... in this case /favicon.ico is used for http://www.chami.com/tips/internet/110599I.html

     

    Since this is entirely optional and not required to render the page it should be perfectly safe to use HTTP::respond 404

     

     

    when HTTP_REQUEST {

     

    if { [HTTP::uri] equals {/favicon.ico} } { HTTP::respond 404 }

     

    }

     

     

    Try it and see how it goes.

     

     

     

Matt_Breedlove_'s avatar
Matt_Breedlove_
Icon for Nimbostratus rankNimbostratus
Aug 01, 2011
Sure, but when the GET request is made, the client is unaware of the size of what a fulfilled response would be. In fact, it could be a totally bogus request. Its not that I want to modify the content of a real server response, its that I want the GET request to go away/dissolve and not even let it get to the server behind the VS. In this case, the request is for /favicon.ico...which actually is a bogus request in that this is not provided by design on the servers, yet the http clients are asking for this in the hopes it is there, which it is not so we just want to nullify the request and move one with page rendering. If we could we would just prevent the client from even making that GET request in the first place

 

 

Thanks

 

M