* Set up CI with Azure Pipelines [skip ci]
* Add other platforms [skip ci]
* Oops, add vmImage back in [skip ci]
* Fix goVersion [skip ci]
* Use sudo to install Go [skip ci]
* Attempt platform-specific Go isntalls [skip ci]
* Try sharing the variable a different way [skip ci]
* Trying this again... [skip ci]
* Fix the PATH [skip ci]
* Fix GOROOT, hopefully [skip ci]
* More fixing [skip ci]
* Still fixing [skip ci]
* Add golang-ci [skip ci]
* asdfasdfasf [skip ci]
* Sigh, work around broken golangci-lint installer [skip ci]
* Try again [skip ci]
* ahhhhhh [skip ci]
* sooooo close! cleanup [skip ci]
* oh c'mon [skip ci]
* thought I had it for a sec [skip ci]
* yaaaayyyy [skip ci]
ship it
* Add upstream header replacements (TODO: tests, docs)
* Add tests, fix a few bugs
* Add more tests and comments
* Refactor header_upstream to use a fallthrough; return regex errors
* Move SiteOutput to a seperate function sorted by port.
* Rename vars and tidy up
* Move loopback note to output loop
* Fix Typo
* Remove unneeded var
* Readability Change
* Change to other port string.
* Simplify as all sites in Server use the same port
* Ensure -quiet supresses fmt.Println calls
* Prevent double output of siteinfo to log - improve log message
* change name of log in comment
* Remove spaces
* Remove extra line output
* final tidy!
* Use caddy.LogDestination to setup log
* Ensure Log is still output if quiet.
* Correct case of functions and make function param bool
* Remove conditional check for LogDestination
* Revert output to simple blocks
* comment update
* Move SiteOutput to a seperate function.
* Simplify as all sites in Server use the same port
* Ensure -quiet supresses fmt.Println calls
* Prevent double output of siteinfo to log - improve log message
* Use caddy.LogDestination to setup log
* Ensure Log is still output if quiet.
* caddytls: Change clustering to be a plugin to the caddytls package
Should resolve the failure in
https://github.com/coredns/coredns/pull/2541.
This change is breaking to clustering plugin developers (not Caddy
users), but logical, since only the caddytls package uses CertMagic
directly (the httpserver package also uses it, but only because it also
uses the caddytls plugin); and it is early enough that no clustering
plugins really exist yet.
This will also require a change of devportal
so that it looks for a different registration function, which has moved
to the caddytls package.
* Remove unused variable
* caddyhttp: Fix test (adjust plugin counting)
* ummmm, remove extra line break
somehow VS Code didn't fmt on save... weird.
Should resolve the failure in
https://github.com/coredns/coredns/pull/2541.
This change is breaking to clustering plugin developers (not Caddy
users), but logical, since only the caddytls package uses CertMagic
directly (the httpserver package also uses it, but only because it also
uses the caddytls plugin); and it is early enough that no clustering
plugins really exist yet.
This will also require a change of devportal
so that it looks for a different registration function, which has moved
to the caddytls package.
* optimized parse cli's disabledMetrics flag string to initTelemetry
* add splitTrim to obtain string slice that not contain empty string
* change TestSplitTrim error output
* gofmt for run_test.go
* restore name of disabledMetrics made more sense
* optimized TestSplitTrim case
* just update splitTrim comment to force CI restart
By using option ca_certificates in proxy block it is possible now to select
CA against which backend certificates shall be checked.
Resolves#1550
Co-authored-by: Danny Navarro <navdgo@gmail.com>
* caddytls: Fix empty SNI handling (new -default-sni flag)
vendor: update certmagic, needed to support this
Hopefully fixes#2451, fixes#2438, and fixes#2414
* caddytls: Don't overwrite certmagic Manager (fixes#2407)
Supersedes #2447
* vendor: Update certmagic to fix nil pointer deref and TLS-ALPN cleanup
* Improve -default-sni flag help text
