RocketChat / RocketChat/Rocket.Chat
Outgoing Integration POST Method send after Connection Close
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
An Outgoing Integration with a POST Method will not send the Content Correclty:
return {
url: request.url,
headers: request.headers,
content: "F1=1",
method: 'POST',
auth: 'xx:xx'
};
TCPDump shows:
host: 192.168.0.xxx
content-length: 4
Connection: close
F1=1
Connection: close is send before the content, data or params.
Server Setup Information:
- Version of Rocket.Chat Server: 0.63.3
- Operating System: Ubuntu 16 LTS
- Deployment Method(snap/docker/tar/etc): snap
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the outgoing integration POST request described in the issue and inspect the integration request-handling entry point that produces the TCPDump sequence. Compare the connection-close timing with the request body transmission; done means the POST content is sent correctly before the connection closes, with a regression test covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100