Parser should reject bogus options
skx opened this issue · comments
Most of our protocol tests allow extra options to be specified:
target.example.com must run $SERVICE with OPTION_NAME OPTION_VALUE
The protocol tests know which options they support, so this should be a parser error, because header is not an option name which is currently supported:
http://example.com/ must run http with header "Foo: 1"
Add a method to our protocol-test to return supported-options and we can rule out lines that have bogus entries.