* 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>
On Firefox, we were seeing an extra large horizontal scrollbar. Didn't happen on Chrome though. I think it's an edgecase bug with Firefox... but I think we can take a better approach that can avoid it anyways.
The CSS for `paper` classes was set up so that they would stack/overlap onto eachother. It was using `left: -100%;` and `left: -200%;` on `paper2` and `paper3`, to stack the next two on top of the first one, all three being relative positioned.
The problem comes because I think Firefox calculates the scrollbar width before relative positioning calculations come into play, so because the elements were rendered way off to the right before being moved over, it would "grow" the page really wide. Go to https://caddyserver.com/docs/ on any browser, element inspector, find `#paper2` and `.paper3`, uncheck the `left` CSS prop on both of those. You'll see that they render over to the right.
An alternate way to do the same thing is to use negative margins to stack the elements. I think margins are calculated earlier, so on Firefox this doesn't cause a scrollbar problem.
I did need to use a `calc()` unfortunately to get it pixel-perfect positioning compared to how it was before, because `#paper1` has `margin-left: 20px` and then `#paper2` inherits that margin so it needs to remove the extra 20px to realign. `calc()` is cheap though. It's fine.
Also, need `z-index: -1;` to make sure the BG papers go behind the page content.
* 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>
