#_webhooks

1 messages ¡ Page 1 of 1 (latest)

hard chasmBOT
#

👋 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/1336159713330593832

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

frigid brook
#

hello! 403 indicates that the server understood the request but refused to process it - http://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403

You'll probably want to look into why your server is returning 403, there's not much insight that we can provide here since we don't know the details of your implementation

MDN Web Docs
403 Forbidden - HTTP | MDN

The HTTP 403 Forbidden client error response status code indicates that the server understood the request but refused to process it.
This status is similar to 401, except that for 403 Forbidden responses, authenticating or re-authenticating makes no difference.
The request failure is tied to application logic, such as insufficient permissions to...

high hound
#

As mentioned in the question, other webhook events receive a 200 response at the same URL.

frigid brook
#

I understand your concern. However, you'll need to investigate why this specific webhook event is returning a 403 error from your server. The response is generated by your server, so it's something only you can address.

high hound
#

The only case where my server returns a 403 response for the given URL is when the HTTP method is PROPFIND. Is the HTTP method for the checkout.session.completed webhook PROPFIND?