cURL

Curiefense includes a command-line tool called curieconf_cli.

If you wanted to get the detailed list of existing configurations you would run:

$ curieconf_cli conf list

You can also just use cURL to accomplish the same task:

$ curl -XGET $api_url/configs/

To view the HTTP headers of any URL all you need to do is run the following with cURL:

$ curl -I https://example.com

The response should look something like this:

HTTP/2 200
accept-ranges: bytes
cache-control: max-age=604800
...
x-cache: HIT
content-length: 1270

If your URL has query strings then you will need to add double quotes:

curl -I "https://example.com?query=string&foo=bar"

I use cURL because it's one of the most portable ways to download resources via HTTP(s)

• @{Go}|tool:1005| because it's easy and simple, facilitates collaboration , and also it's fast, scalable, powerful.
• @{Visual Studio Code}|tool:4202| because it has one of the most sophisticated @{Go}|tool:1005| language support plugins.
• @{Vim}|tool:644| because it's @{Vim}|tool:644|
• @{Git}|tool:1046| because it's @{Git}|tool:1046|
• @{Docker}|tool:586| and @{Docker Compose}|tool:3136| because it's quick and easy to have reproducible builds/tests with them
• @{Arch Linux}|tool:2635| because @{Docker}|tool:586| for Mac/Win is a disaster for the human nervous system, and Arch is the coolest Linux distro so far
• @{Stack Overflow}|tool:1927| because of Copy-Paste Driven Development
• @{JavaScript}|tool:1209| and @{Python}|tool:993| when a something needs to be coded for yesterday
• @{PhpStorm}|tool:1452| because it saves me like 300 "Ctrl+F" key strokes a minute
• @{cURL}|tool:6552| because terminal all the way