caddy-cgi - fork of caddy for nix to build it with the cgi plugin

Age	Commit message (Collapse)	Author
2020-03-04	httpcaddyfile: remove certificate tags from global state (#3111)	Mark Sargent
	* remove the certificate tag tracking from global state * refactored helper state, added log counter * moved state initialisation close to where it is used. * added helper state comment
2020-02-28	httpcaddyfile: Treat no matchers as 0-len path matchers (fix #3100)	Matthew Holt
	+ a couple other minor changes from linter
2020-02-25	v2: 'log' directive for Caddyfile, and debug mode (#3052)	Matt Holt
	* httpcaddyfile: Begin implementing log directive, and debug mode For now, debug mode just sets the log level for all logs to DEBUG (unless a level is specified explicitly). * httpcaddyfile: Finish 'log' directive Also rename StringEncoder -> SingleFieldEncoder * Fix minor bug in replacer (when vals are empty)
2020-02-20	httpcaddyfile: tls: Load repeated cert files only once, with one tag	Matthew Holt
	See end of issue #3004. Loading the same certificate file multiple times with different tags will result in it being de-duplicated in the in- memory cache, because of course they all have the same bytes. This meant that any certs of the same filename loaded with different tags would be overwritten by the next certificate of the same filename, and any conn policies looking for the tags of the previous ones would never find them, causing connections to fail. So, now we remember cert filenames and their tags, instead of loading them multiple times and overwriting previous ones. A user crafting their own JSON might make this error too... maybe we won't see it happen. But if it does, one possibility is, when loading a duplicate cert, instead of discarding it completely, merge the tag list into the one that's already stored in the cache, then discard.
2020-02-16	httpcaddyfile: 'handle_errors' directive	Matthew Holt
	Not sure I love the name of the directive; might change it later.
2020-02-14	caddyfile: Refactor; NewFromNextSegment(); fix repeated matchers	Matthew Holt
	Now multiple instances of the same matcher can be used within a named matcher without overwriting previous ones.
2020-02-12	tls: Add acme_ca_root and tls/ca_root to caddyfile (#3040)	Mark Sargent

2020-02-08	httpcaddyfile: Add support for DNS challenge solvers	Matthew Holt
	Configuration via the Caddyfile requires use of env variables, but an upstream issue is currently blocking that: https://github.com/go-acme/lego/issues/1054 Providers will need to be retrofitted upstream in order to support env var configuration.
2020-02-06	caddyfile: tls: Tag manual certificates (#2588)	Matthew Holt
	This ensure that if there are multiple certs that match a particular ServerName or other parameter, then specifically the one the user provided in the Caddyfile will be used.
2020-01-22	httpcaddyfile: Update directive docs; put root after rewrite	Matthew Holt

2020-01-22	httpcaddyfile: Get rid of 'tls off' parameter; probably not useful	Matthew Holt

2020-01-16	httpcaddyfile: Fix nested blocks; add handle directive; refactor	Matthew Holt
	The fix that was initially put forth in #2971 was good, but only for up to one layer of nesting. The real problem was that we forgot to increment nesting when already inside a block if we saw another open curly brace that opens another block (dispenser.go L157-158). The new 'handle' directive allows HTTP Caddyfiles to be designed more like nginx location blocks if the user prefers. Inside a handle block, directives are still ordered just like they are outside of them, but handler blocks at a given level of nesting are mutually exclusive. This work benefitted from some refactoring and cleanup.
2020-01-09	v2: Implement Caddyfile enhancements (breaking changes) (#2960)	Matt Holt
	* http: path matcher: exact match by default; substring matches (#2959) This is a breaking change. * caddyfile: Change "matcher" directive to "@matcher" syntax (#2959) * cmd: Assume caddyfile adapter for config files named Caddyfile * Sub-sort handlers by path matcher length (#2959) Caddyfile-generated subroutes have handlers, which are sorted first by directive order (this is unchanged), but within directives we now sort by specificity of path matcher in descending order (longest path first, assuming that longest path is most specific). This only applies if there is only one matcher set, and the path matcher in that set has only one path in it. Path matchers with two or more paths are not sorted like this; and routes with more than one matcher set are not sorted like this either, since specificity is difficult or impossible to infer correctly. This is a special case, but definitely a very common one, as a lot of routing decisions are based on paths. * caddyfile: New 'route' directive for appearance-order handling (#2959) * caddyfile: Make rewrite directives mutually exclusive (#2959) This applies only to rewrites in the top-level subroute created by the HTTP caddyfile.
2019-12-13	tls: Ensure conn policy is created when providing certs in Caddyfile	Matthew Holt
	Fixes #2929
2019-12-10	v2: Module documentation; refactor LoadModule(); new caddy struct tags (#2924)	Matt Holt
	This commit goes a long way toward making automated documentation of Caddy config and Caddy modules possible. It's a broad, sweeping change, but mostly internal. It allows us to automatically generate docs for all Caddy modules (including future third-party ones) and make them viewable on a web page; it also doubles as godoc comments. As such, this commit makes significant progress in migrating the docs from our temporary wiki page toward our new website which is still under construction. With this change, all host modules will use ctx.LoadModule() and pass in both the struct pointer and the field name as a string. This allows the reflect package to read the struct tag from that field so that it can get the necessary information like the module namespace and the inline key. This has the nice side-effect of unifying the code and documentation. It also simplifies module loading, and handles several variations on field types for raw module fields (i.e. variations on json.RawMessage, such as arrays and maps). I also renamed ModuleInfo.Name -> ModuleInfo.ID, to make it clear that the ID is the "full name" which includes both the module namespace and the name. This clarity is helpful when describing module hierarchy. As of this change, Caddy modules are no longer an experimental design. I think the architecture is good enough to go forward.
2019-09-30	httpcaddyfile: Add acme_ca and email global options	Matthew Holt
	Also add ability to access options from individual unmarshalers through the Helper values
2019-09-16	httpcaddyfile: static_response -> respond; minor cleanups	Matthew Holt

2019-09-10	caddyfile: Improve Dispenser.NextBlock() to support nesting	Matthew Holt

2019-08-22	Fix SIV where /v2 was missing from caddyfile adapter work (#2721)	Mohammed Al Sahaf

2019-08-21	Refactor Caddyfile adapter and module registration	Matthew Holt
	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.
2019-08-09	Implement config adapters and beginning of Caddyfile adapter	Matthew Holt
	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.