* docs: Changes for v2.5.2 release
* docs: Remove -X POST
Curl automatically uses POST for -d and --data-binary.
I intentionally left it in to be explicit to learners, but
maybe best practices are better.
* api: /adapt endpoint and Etag usage
* api: Minor tweaks
* Alright fine
* Clarify Etag usage
* CEL embedded matchers
* Oops
* Lots more adjustments
Co-authored-by: Francis Lavoie <lavofr@gmail.com>
* docs: Some random polish
Just a bunch of little things that I think would help users from frequently asked forum questions.
* Adjustments, fix `tls_server_name` docs
* Update src/docs/markdown/caddyfile/concepts.md
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
* docs: Add cert getters to tls (tailscale, http)
* Rename "getter" modules to "manager" modules
* Fix ID
* Add note on automatic-https page
* loopback -> local
* Minor tweaks
* Clarify that enabling tailscale is not necessary
* More clarifications
* Add documentation for tracing directive
* Update header in tracing.md
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
* Update documentation in tracing.md
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
* add link to the repository
* add link to gRPC repo and w3c specification
Co-authored-by: Andrii Kushch <>
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
Pairs with https://github.com/caddyserver/caddy/pull/4436.
I could split these changes in two, some changes should only land in 2.5.0, but others are pure documentation that could be pushed live now. But 🤷♂️ I think it's fine for these to wait until 2.5.0, what's another month or whatever? 😅
* docs: Adjustments to global options docs, for clarification
* Apply suggestions from code review
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
Co-authored-by: Matt Holt <mholt@users.noreply.github.com>
* Update reverse_proxy.md
Documantion says: "By default, Caddy passes thru incoming headers [...], with two exceptions:". But technically there is another another header that is added (if not present): `Accept-Encoding`.
When the client is a web browser this header should be already set. But for curl or similar tools, that might not be the case.
* Update src/docs/markdown/caddyfile/directives/reverse_proxy.md
Perfect!
Co-authored-by: Francis Lavoie <lavofr@gmail.com>
Co-authored-by: Francis Lavoie <lavofr@gmail.com>
* docs: Add new Linux Service page, moved from install.md
* Apply suggestions from code review
Co-authored-by: Carl George <carl@george.computer>
* Add note regarding resetting Exec*
* Updates to make the page more generalized
Docker
* Polish the Windows Service docs a bit
Co-authored-by: Carl George <carl@george.computer>
