This logic only exists in the Plug, so attempting to validate the signature by calling the library function HTTPSignature.validate_conn/2 directly will never work because we do not attempt to construct the (request-target) and @request-target headers with both the commonly misinterpreted and correct implementation of this field. Therefore all attempts to validate a signature from an Oban Job will fail. |
||
|---|---|---|
| .. | ||
| benchmark.exs | ||
| config.exs | ||
| description.exs | ||
| dev.exs | ||
| docker.exs | ||
| dokku.exs | ||
| emoji.txt | ||
| prod.exs | ||
| test.exs | ||