Fabrice Reix
Fabrice Reix
yes, we have the objective to support all curl features but only related to HTTP. What is your usecase?
From your last comment, we can implement `--resolve` for the next release (#379)
We like that too "filter" functions which can take input from a previous pipe with possible parameters between brackets We are in the process of generalizing templates everywhere in the...
The json body { ...} is equivalent to the following assert: `body equals "{...}" Therefore, this is an assert on a string (not a json). The error message could maybe...
Hello, in fact, it is already working with Linux/bash. Here is the run of your example. ``` $ ./test.hurl error: Assert Http Version --> test.hurl:5:6 | 5 | HTTP/1.1 302...
Hello @jasonkarns, It could be indeed a good output format for Hurl tests. It seems suited for command-line apps. Do you have any samples input Hurl file/TAP expected output? Thanks
Hi, The `body` query in your sample (line 5) returns a String. That explains the given error. We would need to capture a JSON object instead. It might be a...
Yes! we'll definitely add it. we have really the benefit of using libcurl.
Option `--cacert ` has now been added (#314) Only PEM format is supported for the time-being. We will support more in the future and also add the option `--capath`.
There is nothing specific to self-signed certificates in Hurl. You could use [-k](https://hurl.dev/docs/man-page.html#insecure) to ignore the SSL warning.