Fabrice Reix
Fabrice Reix
Hello, Yes, we could treat the Hurl Object as a JSON Object implicitly and apply jsonpath on it. We will have to convert each of its value to a JSON...
We can support $XDG_CONFIG_HOME/hurlrc
Relating to the precedence between environment variables and config file. Defining proxy in curl config file (`~/.curlrc`) seems to take precedence over environment variable `http_proxy` (But it could be specific...
we can even add one if we add the option `--config` (same as curl) (just before comand-line)
also in favor if the 2nd solution
@jcamiel @lepapareil Related to using a standard Hurl string value for url, do we also apply the following changes? - `http://` or `https://` protocol prefix not checked anymore at parse-time...
I think the `http://` prefix check was simply here to fail as early as possible with nice error message.
Thanks @niklasweimann for reporting the bug. We initially added several checks to focus on http/https protocol. But for sure, we should accept any Location header when we do not follow...
The comparisons are already text-based. Like curl, following redirect is turned off by default and explicitly turned on with [--location](https://hurl.dev/docs/manual.html#location) option. The assert and the redirect should be independent of...
Thanks @lu-zero for reporting the bug. Could you please give us the JSON response so that we can reproduce it?