#husani0nl9_webhooks
orchid etherBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1392538797413105805
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- husani0nl9_webhooks, 21 hours ago, 21 messages
rocky stump
Hi there, let me take a look.
loud idol
Kk!
rocky stump
So looking at the event, the server (Google Frontend) is returning a 400 error: Invalid encoding: ISO-8859-1
The request header is not empty.
Let me double check.
loud idol
Yeah, I'm returning that 400 Error. My servlet gets "com.stripe.exception.SignatureVerificationException: Unable to extract timestamp and signatures from header" when running "Webhook.constructEvent(payload, sigHeader, endpointSecret);"
None of my code had changed when this issue started happening. I added "request.getHeader("Stripe-Signature");" and it's giving me an empty string.
rocky stump
Ok, this is something you'll need to investigate on your end unfortunately. I was digging internally, and there's nothing on our end. The error can be caused by anything. It's not something we can investigate or debug on our end because we don't have access to your server. Even though you did not make any code changes, it's possible there were changes on the server side.
loud idol
Oh no... 🙁
Can you at least tell if the "Stripe-Signature" is being sent in the request header on your end?
loud idol
Alrighty, then! Thanks for the info.
Yeah, I'll start digging on my end
I was just confused/worried I'd be looking for an issue that I couldn't find/solve because this started happening out of nowhere.
loud idol
`Stripe-Signature: t=1751981124,v1=ad9c097a9dc.....`
But that confirmation is enough for me.
Thank you!
rocky stump
I understand. These issues can be the worst. Sorry we couldn't help further.
loud idol
No worries. Appreciate you tons!
orchid etherBOT
loud idol
Hey! Since this thread is still open, I wanna put this for anyone else to reference in the future.
I found the issue: For some reason the "Stripe-Signature" header name is now being turned lowercase. My platform is Google AppEngine Standard and I'm still trying to see if I can find out why that changed, but that was the root cause.
orchid etherBOT