Can iRule Reject Requests Based on 'True-Client-IP'

RFC2616 states that you should send a 403 for this case. But what you actually use is up to you. 404 could be appropriate. Just make sure to set cache control headers if you use a 404 to prevent proxies from caching the response.

 

 

HTTP::respond 404 Cache-Control No-Cache Pragma No-Cache

 

 

 

http://tools.ietf.org/html/rfc2616section-10.4.4

 

 

10.4.4 403 Forbidden

 

 

 

The server understood the request, but is refusing to fulfill it.

 

Authorization will not help and the request SHOULD NOT be repeated.

 

If the request method was not HEAD and the server wishes to make

 

public why the request has not been fulfilled, it SHOULD describe the

 

reason for the refusal in the entity. If the server does not wish to

 

make this information available to the client, the status code 404

 

(Not Found) can be used instead.

 

 

10.4.5 404 Not Found

 

 

The server has not found anything matching the Request-URI. No

 

indication is given of whether the condition is temporary or

 

permanent. The 410 (Gone) status code SHOULD be used if the server

 

knows, through some internally configurable mechanism, that an old

 

resource is permanently unavailable and has no forwarding address.

 

This status code is commonly used when the server does not wish to

 

reveal exactly why the request has been refused, or when no other

 

response is applicable.

 

 

 

 

 

Aaron