You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that my secret is no longer valid after the webhook traverses the proxy. Would it be possible to preserve the secret so i can also validate with my listener running on internal kube ?
The text was updated successfully, but these errors were encountered:
gnieto
added a commit
to gnieto/GitWebhookProxy
that referenced
this issue
Apr 8, 2022
Previous implementation was preventing to proxy signature headers,
unless some secret was set up.
By forwarding all the known GitHub headers, upstream service can do this
checks. Note that this do not break the signature validation on this
proxy.
I've also added the sha256 signature header to the list of known GitHub
headers.
Fixes: stakater#94
I noticed that my secret is no longer valid after the webhook traverses the proxy. Would it be possible to preserve the secret so i can also validate with my listener running on internal kube ?
The text was updated successfully, but these errors were encountered: