#gabs_webhooks-encoding

1 messages ยท Page 1 of 1 (latest)

floral ibexBOT
#

๐Ÿ‘‹ 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/1216873492209995869

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

oak acornBOT
frosty star
#

@small vapor our button just resends the Event. The error likely comes from your own server/code itself not properly parsing the data as UTF-8

#

gabs_webhooks-encoding

small vapor
#

The part I don't get is why regular webhook events triggered application code previously, and now it doesn't get anywhere near the application code when I resent the event via the Dashboard

#

I am waiting for a regular event to come through to validate this

frosty star
#

Do you have an Event id I can look at?

small vapor
#

evt_1OqyexGa7qzGHbgmm4hVfnCt

frosty star
#

yeah right now your own server is rejecting our HTTP request really

#

There isn't much more I can give you. We make a request to your server/CDN/whatever and that returns "invalid encoding"

small vapor
#

Do you see any difference to this event: evt_1Orw7V2ej2SDXXn6ipBpah0g

frosty star
#

not sure what you mean, that Event has the exact same behaviour/errors

oak acornBOT
small vapor
#

evt_1Orw7V2ej2SDXXn6ipBpah0g was sent by automatically yesterday to our system. It triggered application code where and error in our integration was exposed. Today this error was addressed and I am attempting to resend an event to validate the fix.

For some reason the request sent when resending evt_1Orw7V2ej2SDXXn6ipBpah0g now behaves completely differently and yes our server seems to be rejecting it's encoding

But my question is - why is the request using different encoding?

fickle raptor
#

Hi ๐Ÿ‘‹

My colleague needs to go so I'm stepping in

small vapor
#

Np

fickle raptor
#

why is the request using different encoding
I'm not sure what you are referring to here. We have not changed anything about the webhook event payload. But your server is responding with {"code":500,"message":"Internal Server Error"}

frosty star
#

We always send Events encoded as UTF-8. This has been true for over 10 years.

#

the problem is that your own server is currently not understand UTF-8 and so it rejects the data. You need to ensure you configure your server to receive/parse UTF-8 instead

small vapor
#

Ok thanks for your time - ill dig into this more on our side

#

Just FYI - this event just hit our servers automatically and it had the right encoding: evt_1OtHbi2cYYpbgKdeM1VZE2HL