Blake Burkhart

This is arguably a duplicate of #77, but this crash is triggered by a different sequence of actions. The crashing code is possibly the same.

This is only an issue because github doesn't have arbitrary fields in the bug tracker. You really want 100 issues all called NullPointerException? And what do I title issues for...

That said, as long as the exception is mentioned in the text of the issue it's searchable. Which means, actually search before making issues. But there is still a question...

Yes, that can get us pretty far. I may try out implementing that. I'm trying to decide if we should actually put it in the DB, or make the test...

I'm not sure what the desired behavior is, but this change to `options.js` would allow the following to work: ```shell FOO=false FOO=true FOO=bar # Uses the default value FOO= ```...

Commander may need to be updated to 3.0.0+ too, I didn't test this. https://github.com/tj/commander.js/pull/987

I wish this was a built in command. Updating the most recent deployment seems like it should be built in. Currently I'd have to do something like this hack to...

I see #61 was closed. I agree that it isn't required to prevent the user from using inappropriate certs based on usage, but I would suggest making this information available...

Currently only HTTP headers `request->attributes().request().http().headers()` may be matched. I think an enhancement could be to allow matching on `request->attributes().destination().principal()` (or anything in the request attributes). For the specific use case...

I think RFC 3982 and RFC7230 only say header "field names" are case-insensitive, not the field value. You have to read the spec to determine how to match each header....