remo

This first beta release brings the ability to
import ModSecurity audit-logs and match them
against the ruleset in the edit-area of Remo. This
lets you check if the ruleset which you are
developing will work with your online application
in practice.

This release includes a group of predefined
standard regular expressions that make editing of
requests a lot easier. The responses to every
argument failure can be configured specially,
including HTTP status code and optional redirect
location. Argument names can now contain regular
expressions themselves in order to map tabular
forms with dynamic content in remo.

Support for query string arguments and cookies. Every request argument can now be optional or mandatory. With this, Remo can qualify basic HTTP requests completely: method, path, query string parameters, headers, post payload parameters, and cookies.

The GUI has support for POST arguments, and generates a rule for a single request (generate button next to the request path). The rule generator has support for POST arguments.

New features in the GUI include support for HTTP
headers in the remo edit window, a customizable
list of default headers and default value domains,
in-place editing for all supported request
properties (method, path and headers), and labels
for toolset buttons. Detailarea has been removed.
New features in the rule generator include strict
checking of headers in the generated ModSecurity
ruleset, and a per request rule-group in the
ruleset using the LocationMatch directive.