I would like to be able to prevent certain headers (Authorization: X-Auth-Token:, etc ) from being included in the caddy logs.

I found caddyserver/caddy#3562, which is asking to be able to set an allowlist of headers, which makes sense for their use case.

In my case, a blocklist, makes more sense, as I only want to prevent a single header from being included in the

I like how Simplepush presents a couple of different ways to generate push messages on their website:

https://simplepush.io/#libraries

How about having a similar feature directly in the server GUI? That would include the bits documented here https://gotify.net/docs/pushmsg

Quorum doesn't return a message error clearly specifying the cause of an error (from a user standpoint) when the transaction manager fails to Quorum (e.g: 400 bad request, ...).

System information

Release: 2.2.3

Expected behaviour

Helpful error message

Actual behaviour

invalid argument 0: json: cannot unmarshal non-string into Go value of type common.Hash

E.g. accept missing leading 0

In osx/updater/updater.go, we're referencing an ancient Go package, which has moved to a new location. Right now, the updater doesn't build (should we test this on travis?).