|ISTAG||greasyspoon-1.0.1-b01||Provides a way for ICAP servers to send a service-specific "cookie" to ICAP clients that represents a service's current state. It must NOT exceed 32-byte-maximum alphanumeric string of data. An ICAP client should flush all cached data when detecting an change on this tag.|
|Service||GreasySpoon ICAP Server||ICAP Service description|
|Service-ID||1.0.1-b01||A short label identifying the ICAP service. Used by some ICAP clients|
|Options-TTL||180 (seconds)||Set how frequently ICAP clients will ask for ICAP parameters update|
|Max-Connections||100||Defines how much ICAP parallel connections GreasySpoon will support. To adapt regarding mainly memory allocated to GreasySpoon.|
|Keep-Alive||enable||Set if ICAP keep-alive will be supporterd. Default is enable, set to "off" or "disable" to disable it.|
|Preview||0||Set content asked in preview mode. Preview is used to check if traffic match a defined rule before asking for content.
Tip: configure a minimal preview of 48 (bytes) when using MimeMagic to optimize processing.
|path||conf;serverscripts;||Path added to greasyspoon environment|
|maxtimeout||5000 (milliseconds)||Defines overall processing time allocated to scripts in ms. Scripts are aborted if this value is exceeded (valid changes are kept)|
|errorthreshold||10||Successive error threshold after which a script is considered as invalid and automatically disabled. Set to 0 to disable it.|
|bypassonerror||true||Set GreasySpoon behaviour when encountering an error. Default is to bypass service (original content is returned to client. If set to false, returns an ICAP 500 error instead.|