| Age | Commit message (Collapse) | Author |
|---|
|
Fixes #2011
|
|
|
|
|
|
This is unless each route's matcher is dynamically executed after
previous handlers...
|
|
Use piles from which to draw config values.
Module values can return their name, so now we can do two-way mapping
from value to name and name to value; whereas before we could only map
name to value. This was problematic with the Caddyfile adapter since
it receives values and needs to know the name to put in the config.
|
|
|
|
Along with several other changes, such as renaming caddyhttp.ServerRoute
to caddyhttp.Route, exporting some types that were not exported before,
and tweaking the caddytls TLS values to be more consistent.
Notably, we also now disable automatic cert management for names which
already have a cert (manually) loaded into the cache. These names no
longer need to be specified in the "skip_certificates" field of the
automatic HTTPS config, because they will be skipped automatically.
|
|
Differentiating middleware and responders has one benefit, namely that
it's clear which module provides the response, but even then it's not
a great advantage. Linear handler config makes a little more sense,
giving greater flexibility and simplifying the core a bit, even though
it's slightly awkward that handlers which are responders may not use
the 'next' handler that is passed in at all.
|
|
See https://github.com/golang/go/wiki/Modules#semantic-import-versioning
|
|
|
|
Removes the version from the package name
|
|
|
|
|
|
Also flag most fields with 'omitempty' for JSON marshaling
|
|
|
|
|
|
|
