| commit | 2c19d10a730c6f8bd95d8501f1211cd502e1b5d5 | [log] [tgz] |
|---|---|---|
| author | Daniel Gruno <humbedooh@apache.org> | Wed Feb 24 22:12:41 2021 +0100 |
| committer | GitHub <noreply@github.com> | Wed Feb 24 22:12:41 2021 +0100 |
| tree | f5d42dd183545ad620bbf43eb273b71792be6506 | |
| parent | b6b20f847de416612f80a49d1fc1a22d43c60181 [diff] |
Update README.md
Aardvark Proxy Middleman
This service acts as a middleman between frontend web servers and ticket submission services such as JIRA or BugZilla, and intercepts all data sent. Data is scanned for known offending words that are common in spam, and blocks the request if such are found.
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:
# Send all POST requests through Aardvark RewriteEngine On RewriteCond %{REQUEST_METHOD} POST RewriteRule ^/(.*)$ http://localhost:4321/$1 [P] # Rest goes to backend directly ProxyPass / http://localhost:8080/foo/bar/