Jean-Christophe Amiel

``` Executed files: 50 Executed requests: 50 (5.8/s) Request duration: 4000 ms average: 976 ms median: 701 ms min: 976 ms max: 701 ms p90: 100 ms p95: 100 ms...

Great, we can update with : - default hard-coded options in binary - environment variables / terminal - config file - command-line - (file options sections - to be implemented)...

Hi @Baklap4 Regarding options, the current behaviour is that options defined on a specific request take precedence over options defined on command line. For instance, given this file: ```hurl GET...

Hi @simonzkl This could be potentially difficult to implement: for instance, in `--test` mode, tests are run in parallel and the list of all tests to execute is constructed at...

Hi @simonzkl you can work on it as a POC of course, but with really none guarantee that it will be merged. We take our time by discussing the uses...

Hi @linkdd I think I prefer to have a dedicated `socks5` option to match _exactly_ the curl option name ```hurl GET https://example.com [Options] socks5: localhost:8012 HTTP 200 ```

Yes we can check what is the behavior of curl in this case and try to match it.

@linkdd Reviewing the code, I see that we have no restriction on urls passed to `proxy` option. Could you try this syntax ? ``` # Rejection when coming from 192.168.2.0/24...

Hi @GGoetzelmann Thanks for this very detailed description. There is actually no logic in multiline string, characters that are between ` ``` ` markers are taken "as it" from the...

Hi @sify21 This could be indeed useful but, as the same time, we're planning to remove `--interactive` as we're not testing it / using it and it bring some complexity...