Feature Requests

Open Feature Requests

Authentication and session support in Remo

Cover performance issues

Remo is getting really slow, when you have a ruleset with lots of requests and "lot" is actually a small number. A workaround and a good practice anyways is to work with regular expressions. The OWA ruleset in development is 8 requests long...

Proxy-mode for on the fly rule development

New CSS with better looks

Bring a decent look to Remo in Internet Explorer

Import mode sure can be exploited easily

There is no real file validation so far. This has to be done.

Better default value domains

Polish the application

Option to include core ruleset

Ofer Shezaf via modsec-list. OferS@Breach.com, 2007-02-12

Ryan Barnett writes (Ryan.Barnett@Breach.com, 2007-02-21)

http://www.modsecurity.org/blog/archives/2007/02/handling_false.html.
It would make sense to integrate your REMO whitelisted rules in a custom
rules file as described in the Blog so that they work along side the
Core Rules.

Closed Feature Requests

Text "generate button"

Ofer Shezaf via modsec-list. OferS@Breach.com, 2007-02-12

Adressed in Task40Start.

LocationMatch usage simplifies rules and is more efficient

Ofer Shezaf via modsec-list. OferS@Breach.com, 2007-02-12

<LocationMatch "^/index.html$">
  SecRule REQUEST_METHOD "^GET$" "allow,nolog,id:2"
</LocationMatch>

It is important to place the fallback rule also in a LocationMatch. Otherwise it will trigger before the LocationMatch rules...

Also, the SecRule works with default transformation t:lowercase. (-> get instead of GET).
It has to be switched off with t:none: ->

SecRule REQUEST_METHOD "^GET$" "allow,t:none,nolog,id:2"