-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chainhook is not forwarding the auth header to webhook url for stacks predicates #438
Comments
It looks like we only forward the |
MicaiahReid
changed the title
Chainhook is not forwarding the auth header to webhook url
Chainhook is not forwarding the auth header to webhook url for stacks predicates
Oct 11, 2023
MicaiahReid
added a commit
that referenced
this issue
Oct 11, 2023
🎉 This issue has been resolved in version 1.1.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
vabanaerytk
added a commit
to vabanaerytk/chainhook
that referenced
this issue
Aug 7, 2024
## [1.1.1](hirosystems/chainhook@v1.1.0...v1.1.1) (2023-10-11) ### Bug Fixes * add auth header for stacks hook ([#444](hirosystems/chainhook#444)) ([3d0ad07](hirosystems/chainhook@3d0ad07)), closes [#438](hirosystems/chainhook#438) * don't evaluate transactions for block predicates ([#445](hirosystems/chainhook#445)) ([ac3d726](hirosystems/chainhook@ac3d726)) * redis conn ([#442](hirosystems/chainhook#442)) ([5e6d704](hirosystems/chainhook@5e6d704))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@micaiah There is a customer who is saying their auth header is not being added to the requests to their webhook url
Here is what platform is sending to chainhook api
Here is the customer's predicate json, which I uploaded using the file upload feature
It seems like platform is sending the data correctly. Can you check this from your side please?
Here is the link to the thread in Discord - https://discord.com/channels/621759717756370964/1086336958546071666/1161310372700110879
cc @sabby
The text was updated successfully, but these errors were encountered: