proxy_url
: The backend service to proxy to if request is sanespamurls
: Specific honey-pot URLs that trigger a block regardless of the actionignoreurls
: Specific URLs that are exempt from spam detectionpostmatches
: A list of keywords and/or regexes that, if matched, will block the requestmultimatch
: A combination blocker. If a required
keyword or regex is matched, the request will be blocked only if one or more auxiliary
keywords/regexes are also matchedTo enable as a pipservice, add the following minimal hiera yaml to your node config:
pipservice: aardvark-proxy: tag: main
As Aardvark is a proxy middleman for specific purposes, you will preferably need a web server in front. The example below relays all POST requests for /foo/bar through Aardvark, while letting all GETs etc go directly to the backend service.
Assuming Aardvark is listening on port 4321
and the real backend service is on port 8080
:
<Location /foo/bar/> # Send all POST requests through Aardvark <Limit POST> # ProxyPass to Aardvark. Remember that because of <Location ...> the ProxyPass directive is altered. ProxyPass http://localhost:4321/foo/bar/ </Limit> # Send all non-POST requests directly to backend <LimitExcept POST> ProxyPass http://localhost:8080/foo/bar/ </LimitExcept> </Location>