Eric Mrak
Eric Mrak
I would like this, too.
Yes please. Is this mergeable?
You can use the `file` option for the response so that you aren't writing SOAP in json or yaml
It sounds like you want the fallback to your non-existent `file` option to also be a `file` instead of just the regular `body` option?
I'll accept a pull request that allows `file:` to be a `String` or `Array` of filepaths in order of fall-back precedence. ```yaml response: status: 200 file: - "first/file.json" - "second/file.json"...
I have changed the name of the flag to `-H/--case-sensitive-headers` and pushed to `master`. I have included your contribution information. Let me know if this is sufficient for your purposes.
You should be able to use a wildcard `url`; it is just a regex match.
You can do this now on the CLI with `cat`: ``` stubby -d
Is the client is sending those ~query~ form params with the brackets?
That's a good suggestion. Responding to something like `SIGUSR1`/`SIGHUP`/`SIGWINCH` for the cli invocation would be good, too.