Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

Responses for incoming message webhook have no content type #2132

Open
smoyte opened this issue Jun 29, 2021 · 1 comment
Open

Responses for incoming message webhook have no content type #2132

smoyte opened this issue Jun 29, 2021 · 1 comment
Assignees

Comments

@smoyte
Copy link

smoyte commented Jun 29, 2021

Are you sure this is an issue with the Botkit core module?

Yes

What are you trying to achieve or the steps to reproduce?

Receive message from Twilio

What was the result you received?

11200 error, no content type given. curl shows there is no content type in the response:

< HTTP/1.1 200 OK
< Server: nginx/1.14.0 (Ubuntu)
< Date: Tue, 29 Jun 2021 15:17:06 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< X-Powered-By: Express
< 

The request still works, but my Twilio console is littered with errors.

Is this my setup somehow or does this happen to everyone?

If these are empty responses, shoudn't they be 201 or 204?

Context:

  • Botkit version: 4.6.1
  • Messaging Platform: Twilio
  • Node version: 12
@smoyte smoyte changed the title Twilio Responses for incoming message webhook have no content type Jun 29, 2021
@stale
Copy link

stale bot commented Jan 9, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 9, 2022
@benbrown benbrown self-assigned this Mar 23, 2022
@stale stale bot removed the stale label Mar 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants