Skip to content
This repository was archived by the owner on Jun 19, 2023. It is now read-only.

chat.PostMessage: Switch to HTTP POST instead of GET #93

Closed
BrandonBoone opened this issue Sep 2, 2020 · 1 comment
Closed

chat.PostMessage: Switch to HTTP POST instead of GET #93

BrandonBoone opened this issue Sep 2, 2020 · 1 comment

Comments

@BrandonBoone
Copy link

Ran into an issue recently using Noobot where I hit Slack's max URL length calling chat.postMessage. Seems this limit could be increased by switching to use an HTTP POST on the call to chat.postMessage and sending the payload as JSON which supports up to 40,000 characters in its text parameter: https://api.slack.com/methods/chat.postMessage

If you're open to PR's I may be able to make this adjustment.

@BrandonBoone
Copy link
Author

Apologies, this looks like a dupe of #83. I'll close and pick up the conversation there.

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

1 participant