Short text
In the standard version, response pages with HTTP error code 404 (not found) are stored as UFOs (unfound objects) in the cache (adopted into the UFO list), and from then on the error page is sent to the client from the cache.
Parameter Description
You can use this parameter to treat other HTTP error codes as UFOs (for example, 500, internal server error).
The character string contains the HTTP error codes, separated by commas.
Normally only those objects that have triggered the HTTP error code 404 (not found) in the back-end are included in the UFO list.
Example
icm/HTTP/server_cache_0/ufo_codelist = 404,500
This setting means that also requests that triggered error 500 ((internal server error) in the back-end are included in the UFO list. This means they are not in the back-end any longer.
Application Area
Internet Communication Manager
Default Value
404
Values allowed
‘,’ separate list of HTTP error codes
