+49 228 5552576-0


info@predic8.com

request

Description

Interceptors are usually applied to requests and responses. By nesting interceptors into a <request> Element you can limit their applictaion to requests only.

Can be used in

if, proxy, registration, request, response, serviceProxy, soapProxy, stompProxy, swaggerProxy and transport

Syntax

				<request>
				  [interceptors]*
				</request>
Listing 1: request Syntax

Sample

				<serviceProxy port="2000">
				  <request>
				    <regExReplacer regex="Hallo" replace="Hello" />
				    <transform xslt="customer2person.xsl" />
				  </request>		
				</serviceProxy>
Listing 2: request 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

See also

Copyright © 2008-2015 predic8 GmbH
Moltkestr. 40, 53173 Bonn, Tel. +49 (228) 555 25 76-0