Bob Aman

One lightweight improvement might be to allow a resource to simply have multiple routes associated rather than duplicating it.

In retrospect, #73 probably should have been eliminated in favor of this issue, with flag values that default to prefix matching and ignoring trailing slashes. Instead, the default flag in...

It might also be worth trying to figure out if we can do case-insensitive matching, though this may not be a particularly common need.

#47 in particular is highlighting the need for this.

Due to the root cause discovery in #236 and this being dependent on #233 for a resolution, this has been delayed to the 0.6.0 release instead.

The initial problem was with the `HeaderValue` protobuf. Previously it carried things in the `value` field, but switched to the `raw_header` field, leaving the `value` field empty. This applied to...

The secondary issue turned out to be that processing mode overrides are now ignored by default and a new configuration option, `allow_mode_override` was added to return to pre-1.27 behavior. Trying...

Notably this is an issue that was identified in the `api-refactor` branch, but may also exist in the `main` branch. This issue should be tackled after that branch is merged...

Alternatively, maybe this should happen in a subcommand, something like `bulwark-cli check` and that could be run at startup before the server command?

The `verify_http_domains` and `verify_remote_state_prefixes` functions should take a `BTreeSet` parameter instead.