response
Description
Interceptors are usually applied to requests and responses. By nesting interceptors into a <response> Element you can limit their applictaion to responses only.
Can be used in
if, proxy, registration, request, response, serviceProxy, soapProxy, stompProxy, swaggerProxy and transport
Syntax
<response> [interceptors]* </response>
Listing 1: response Syntax
Sample
<serviceProxy port="2000"> <response> <regExReplacer regex="Hallo" replace="Hello" /> <transform xslt="customer2person.xsl" /> </response> </serviceProxy>
Listing 2: response Example
Child Elements
| Position | Cardinality | Description | Element |
|---|---|---|---|
| 1 | 0..* | accessControl, adminConsole, analyser, apiManagement, authHead2Body, balancer, basicAuthentication, cache, clamav, clusterNotification, counter, dispatching, exchangeStore, formValidation, groovy, headerFilter, http2xml, httpClient, if, index, interceptor, limit, log, login, oauth2Resource, oauth2authserver, rateLimiter, regExReplacer, request, response, rest2Soap, reverseProxying, rewriter, ruleMatching, soap2Rest, soapOperationExtractor, soapStackTraceFilter, spdy, statisticsCSV, statisticsJDBC, statisticsProvider, stompClient, swaggerRewriter, switch, tcp, testService, throttle, tokenValidator, transform, urlNormalizer, userFeature, validator, wadlRewriter, webServer, webServiceExplorer, webSocket, wsdlPublisher, wsdlRewriter, xmlContentFilter, xmlProtection or custom elements |