Forum Discussion

Ben_Wilson_2412's avatar
Ben_Wilson_2412
Icon for Cirrus rankCirrus
Jul 11, 2013

Changing HTTP Reponse status code

Hi,   I've been asked to change the reponse HTTP Status code for custom 404 pages to "404" instead of 200.   It looks like this is possible by checking if the request is for /404.jsp, capturing...
application delivery
dev
devops
irules
Ben_Wilson_2412's avatar
Ben_Wilson_2412
Icon for Cirrus rankCirrus
Jul 11, 2013

Sure, right now what's in place is:

 

 

when HTTP_RESPONSE {

 

if { [HTTP::status] == "404" or [HTTP::status] == "501" }{

 

HTTP::redirect "/error/404.jsp"

 

}

 

}

 

 

So what's happening is the 404 response is getting intercepted and replaced with a 302 with the error page URL.

 

Since the error page exists, when the 302 is followed, you'll get a 200 from that request.

 

 

From the client's perspective, they asked for a resource that didn't exist, received a redirect and then a valid response. The valid response is an error page which is obvious to a user, but to an automated system, it appears as though the request was valid.

 

 

Does that make more sense?

 

 

Thanks,

 

Ben