tls_https
Skill3 starsChanged 3 months agoMITView on GitHub
When the server's TLSConfig is set, Start() serves HTTPS on the configured address. WithTLSServer runs a second listener with its own address, sharing the same routes and middleware: Stop() / StopWithContext(ctx) gracefully shut down both listeners. With clientAuth: true, the CA in caFile verifies presented client certificates. Inspect the peer in a handler: The *Okapi struct has no exported fields, so supply a pre-built *http.Server instead of assigning to one: okapi.WithTLS(certManager.TLSConfig()) works the same way when you don't need to…
In this repository20 other files it gives its agents.
- authenticationSkill
- cliSkill
- contextSkill
- dynamic_routesSkill
- error_handlingSkill
- http_clientSkill
- middlewareSkill
- openapiSkill
- overviewSkill
- request_bindingSkill
- responseSkill
- route_definitionSkill
- routingSkill
- sse_streamSkill
- std_compatSkill
- templatingSkill
- testingSkill
- validationSkill
- websocketSkill
- web_spaSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
When the server's TLSConfig is set, Start() serves HTTPS on the configured address.
- Very specific: line 132
Keep the ACME http-01 listener on :80 when using autocert, or use a DNS challenge.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Okapi TLS & HTTPS
Loading a TLS Config
func okapi.LoadTLSConfig(certFile, keyFile, caFile string, clientAuth bool) (*tls.Config, error)| Parameter | Description |
certFile | Path to the certificate (PEM) |
keyFile | Path to the private key (PEM) |
caFile | Optional CA certificate for verifying client certs — "" disables |
clientAuth | Require client certificate verification (mTLS) |
HTTPS-Only Server
tlsConfig, err := okapi.LoadTLSConfig("cert.pem", "key.pem", "", false)
if err != nil {
panic(err)
}
o := okapi.New(okapi.WithTLS(tlsConfig), okapi.WithAddr(":8443"))
o.Get("/", func(c *okapi.Context) error {
return c.OK(okapi.M{"status": "secure"})
})
o.Start() // ListenAndServeTLSWhen the server's TLSConfig is set, Start() serves HTTPS on the configured address.
Dual HTTP + HTTPS
WithTLSServer runs a second listener with its own address, sharing the same routes and middleware:
tlsConfig, _ := okapi.LoadTLSConfig("cert.pem", "key.pem", "", false)
o := okapi.Default() // HTTP on :8080
o.With(okapi.WithTLSServer(":8443", tlsConfig)) // HTTPS on :8443
o.Start() // HTTP served in a goroutine, HTTPS in the foregroundStop() / StopWithContext(ctx) gracefully shut down both listeners.
Mutual TLS (client certificates)
tlsConfig, err := okapi.LoadTLSConfig("server.crt", "server.key", "ca.crt", true)
o := okapi.New(okapi.WithTLS(tlsConfig))With clientAuth: true, the CA in caFile verifies presented client certificates. Inspect the peer in a handler:
o.Get("/whoami", func(c *okapi.Context) error {
tls := c.Request().TLS
if tls == nil || len(tls.PeerCertificates) == 0 {
return c.AbortUnauthorized("client certificate required")
}
return c.OK(okapi.M{"cn": tls.PeerCertificates[0].Subject.CommonName})
})Custom *tls.Config (autocert / Let's Encrypt)
The *Okapi struct has no exported fields, so supply a pre-built *http.Server instead of assigning to one:
certManager := autocert.Manager{
Prompt: autocert.AcceptTOS,
HostPolicy: autocert.HostWhitelist("example.com", "www.example.com"),
Cache: autocert.DirCache("certs"),
}
o := okapi.New(okapi.WithServer(&http.Server{
Addr: ":443",
TLSConfig: certManager.TLSConfig(),
}))
o.Get("/", func(c *okapi.Context) error { return c.OK(okapi.M{"ok": true}) })
// TLSConfig is set, so Start() calls ListenAndServeTLS
go http.ListenAndServe(":80", certManager.HTTPHandler(nil)) // ACME http-01 challenge
o.Start()okapi.WithTLS(certManager.TLSConfig()) works the same way when you don't need to customise the rest of the server.
Generating a Development Certificate
openssl genrsa -out server.key 2048
openssl req -new -x509 -sha256 -key server.key -out server.crt -days 365HTTP → HTTPS Redirect Middleware
c.Redirect writes the redirect and returns nothing, so return nil after calling it:
func redirectToHTTPS(c *okapi.Context) error {
if c.Request().TLS == nil {
c.Redirect(http.StatusMovedPermanently, "https://"+c.Request().Host+c.Request().RequestURI)
return nil
}
return c.Next()
}
o.Use(redirectToHTTPS)HSTS
func hsts(c *okapi.Context) error {
c.SetHeader("Strict-Transport-Security", "max-age=31536000; includeSubDomains")
return c.Next()
}
o.Use(hsts)Practices
- Terminate TLS 1.2+ only — set
MinVersionon a custom*tls.Configwhen you build one yourself. - Serve HSTS only over HTTPS, and only once you are sure every subdomain supports TLS.
- Keep the ACME http-01 listener on
:80when using autocert, or use a DNS challenge.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

