http2-utils

Echo server for these random tests

Install:

❯  go get github.com/igor-kupczynski/http2-utils/echo-server

Profit:

❯ echo-server -addr :8080 -healthcheck localhost:8081

# In a different terminal (or a web browser)
❯ curl localhost:8080/foo

HTTP v2 CLI

Install:

❯  go get github.com/igor-kupczynski/http2-utils/http2-cli

Profit:

❯ http2-cli -url "https://host" -auth "username:pass"
Got response 200 over HTTP/2.0
(...)

Self-signed cert generator

Install:

❯  go install github.com/igor-kupczynski/http2-utils/selfsigned-gen@latest

Profit:

❯ selfsigned-gen -domains "example.com,*.example.com"
❯ openssl x509 -subject -enddate -ext subjectAltName  -noout -in domain.pem
  subject=O = "Example, Inc.", CN = example.com 
  notAfter=Oct 21 14:44:26 2029 GMT
  X509v3 Subject Alternative Name: 
      DNS:example.com, DNS:*.example.com

Too many requests

Always close an incoming connection

Install:

❯  go get github.com/igor-kupczynski/http2-utils/too-many-requests

Profit:

❯ too-many-requests -addr localhost:8080 -close -healthcheck localhost:8081

# In a different terminal (or a web browser)
❯ curl localhost:8080/foo

Client TLS (mTLS)

A simple server to experiment with mTLS.

We have a set of certs in client-auth/certs:

• CA
• client (DNSName: client.local), signed by CA
• server (DNSName: localhost), signed by CA

Server

❯ go run client-auth/server.go

Client

Without mTLS:

❯ curl --cacert client-auth/certs/ca.pem https://localhost:8443
Hello, stranger! Here's your random number: 8674665223082153551

With mTLS:

❯ curl --cacert client-auth/certs/ca.pem --cert client-auth/certs/client.pem  --key client-auth/certs/client.key https://localhost:8443
Hello, client.local! Here's your random number: 3916589616287113937