Create [Options] section to use command line option per request

[jcamiel]

In 1.6.1, Hurl has command line options that affect a whole file (i.e each entry of a test).

For instance, --insecure allows to by-pass certificate verification on all entries of a file.

We could add an [Options] section that will allow to set option per request.

For instance:

GET https://trusty.net
[Options]
insecure: true

HTTP/* 200


GET https://not-trusty.net

HTTP/* 200

Will by-pass certificate verification on https://trusty.net and will verify certificate on https://not-trusty.net.

We could expose all the relevant options (excluding those which are not, like --color).

The supported options could be:

GET https://example.org
[Options]
cacert: tmp/certificates/my-cert.cer
compressed: true
connect-timeout: 60
cookie: tmp/cookie-in.txt
cookie-jar: tmp/cookie-out.txt
file-root: /users/bob/tmp
location: true
include: true
insecure: true
ignore-asserts: true
max-redirs: 20
max-time: 30
proxy: localhost:8888
verbose: true

HTTP/* 200

Options that can already be defined per-request should not be included. For instance --user add basic authentifciation to each request.
As there is a [BasicAuth] section wich allows set basic authentification on a request, we don't need to support user in [Options].

Options excluded because there are not relevant per-request:

• --color
• --fail-at-end
• --glob
• --interactive
• --json
• --no-color
• --no-output
• --noproxy
• --output
• --progress
• --report-junit
• --report-html
• --test
• --to-entry
• --to-entry
• --variable
• --variables-file
• --help
• --version

[fabricereix]

This feature is very useful.
It could also set explicitly variables in a Hurl file (#533)

[Options]
variable: name=toto

[fourjay]

This is listed as added to the 1.7 release (yay)
But when trying it out I get

| [Options]
| the section is not valid. Valid values are Captures or Asserts

I'm using the release file for x86-64-linux
hurl-1.7.0-x86_64-linux.tar.gz

[jcamiel]

Hi @fourjay can you provide your Hurl file ?
We're updating the docs on https://hurl.dev for the 1.7.0. But, just for your information, the [Options] sections are relative to a request, for instance:

GET https://foo.com
[Options]
insecure: true
variable: host=toot.com
HTTP/*

# Another request without options
GET http//bar.com

For the moment, you can not use the [Options] sections at the file level without any request. We're going to add it soon. So this Hurl file is not valid:

# Options for the whole file
[Options]
variable: host:sample.com

GET https://{{host}}
HTTP/*

But it'll be soon !

[fourjay]

Placement was the issue :-)
I'd placed the [Options]`` section after the HTTP/1.1```
It works when I put the [Options] directly after the GET request
Thank you!

FWIW, I use hurl for broad service testing, across our many unrelated web services.
The option to use insecure: true on a case by case basis is very helpful.
I know this use case is not the primary driver for the project, but, at least from my view, hurl is a very good match :-)

[jcamiel]

Thanks for the feedback, always happy to hear how Hurl is used in the wild!

[alturkovic]

Hi @fourjay can you provide your Hurl file ? We're updating the docs on https://hurl.dev for the 1.7.0. But, just for your information, the [Options] sections are relative to a request, for instance:

GET https://foo.com
[Options]
insecure: true
variable: host=toot.com
HTTP/*

# Another request without options
GET http//bar.com

For the moment, you can not use the [Options] sections at the file level without any request. We're going to add it soon. So this Hurl file is not valid:

# Options for the whole file
[Options]
variable: host:sample.com

GET https://{{host}}
HTTP/*

But it'll be soon !

Sorry to comment on an old issue, but this is the only place I found the mention of global [Options] which sounds super useful to set input variables and it was mentioned here that it will be supported. Is this still planned? Should I open a feature request for this?

[jcamiel]

Hi @alturkovic this feature is still planned, sure you can open a specific issue on it so we don't forget it!