node-red / node-red/node-red-nodes
node-red-node-xmpp
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
To help us understand the issue, please fill-in as much of the following information as you can:
-->
Which node are you reporting an issue on?
node-red-node-xmpp
What are the steps to reproduce?
in node red xmpp, setup an xmpp server with domain like usually.
What happens?
the redirected domain is taken instead of the dns record domain
What do you expect to happen?
if example.com is my domain and my dns record is xmpp.example.com then the xmpp client must keep example.com domain for asking to xmpp server.
the pb there it asked for xmpp.example.com to my xmpp server.
Please tell us about your environment:
node red under docker container
- Node-RED version:1.03
- node.js version:??
- npm version:??
- Platform/OS: docker
- Browser:brave
Tell me if you need more information or if not clear.
THX.
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 locating the node-red-node-xmpp implementation and reproduce the setup described with an XMPP server, a domain such as example.com, and a DNS record at xmpp.example.com. Clarify the redirect and DNS behavior, then verify that the client preserves the configured domain when requesting the XMPP server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100