request-type

This matches on the type of request the edge server receives. Possible values for the tag are: 'user,' 'esi-fragment,' 'esi-war,' and 'esi-tunnel.'

<match:request-type value="esi-fragment">
</match:request-type>

esi-fragment matches on fragment requests going from ESI->edge server->origin and back from origin->edge server->ESI.

esi-war matches on WAR requests going from ESI->edge server->origin and back from origin->edge server->ESI.

esi-tunnel matches on request-mod (EdgeJava) requests going from ESI->edge server->ej-tomcat and back from ej-tomcat->edge server->user. It's used to forward requests to the local Java app server. This is the only request-type that's not applicable to cache since all request-mod requests go to the local Java app server.

user matches everything else. This maintains backward compatibility with the esi-fragment match type, which matched on whether a request was for a fragment, or not for a fragment. User registers a positive match if the request is not any of the other types (esi-fragment, esi-war, esi-tunnel).

The edge server allows multiple values for the request-type match with a comma separator to indicate that the match should evaluate to true if any of the request types match, for example:

<match:request-type value="user,esi-tunnel,esi-war">

The old match type <match:esi-fragment value="on|off "> was adjusted for backward compatibility so that the 'on' setting is the same as <match:request-type value="esi- fragment"> and the 'off' setting is the same as <match:request-type value="user">