I know the xmpp server and port. And able connect via telnet.
However, when try to query for creating new user or authenticate (existing user), getting error as invalid namespace.
So how to know what are the namespace and XML tags to be used for a given any host.
XML Namespaces aren't specific to an XMPP server. In general, all XMPP servers follow the same XMPP protocol and start by undergoing normal XMPP stream negotiation as specified by RFC 6120. To see this in action, you can start this process by telneting to teh server and sending a new stream:
<?xml version='1.0'?>
<stream:stream
from='juliet#im.example.com'
to='im.example.com'
version='1.0'
xml:lang='en'
xmlns='jabber:client'
xmlns:stream='http://etherx.jabber.org/streams'>
(you'll need to substitute to/from for the appropriate address, of course). The XML namespaces in this start stream element (jabber:client and http://etherx.jabber.org/streams_ are used by all XMPP servers. The server should then respond with its own opening stream; from there you can complete stream negotiation as specified by the RFC.
Related
I'm setting up my own XMPP server on a VPS, mostly for additional control and not for public use. I want to set up HTTP file upload, using an "upload." subdomain. However, attempting to send files gives me a 404. I'm using prosody-filer.
I am looking for a working reference sample MSMQ remote receive and remote send with transactional support and transport level security.
I have looked into Microsoft documentation and it talks about Message Encryption in theory but I couldn't see a sample.
I knew about WCF implementation however it does only MSMQ as a transit during client to server whereas I am looking for a console client to push a message from a server and later the message could be received by some other client from another server.
Thanks in Advance.
I saw many Tunnel to host:443 in Fiddler traffic interception, when I click it I saw below info:
The selected session is a HTTP CONNECT Tunnel. This tunnel enables a client to send raw traffic (e.g. HTTPS-encrypted streams or WebSocket messages) through a HTTP Proxy Server (like Fiddler).
I also searched this -
Fiddler2: Decrypt HTTPS traffic and Tunnel to host:443
But these didn't answer my question, why do we need the HTTP CONNECT Tunnel? Why does a client need to send raw traffic?
See https://textslashplain.com/2015/11/19/understanding-connect-tunnels/
tl;dr: Browsers need to send CONNECT tunnel requests to proxies in order for the proxy to know to what server the traffic should be sent.
The encryption provided by HTTPS prevents the proxy server from seeing the URLs or HOST headers of the requests, and these are how a proxy normally decides where to send the requests. So, for HTTPS traffic, a different approach is needed-- that approach is that the client tells the proxy: "Hey, give me a tunnel to example.com and let me know when it's ready." The proxy does so and tells the client HTTP/200 Connection established. At that point, the proxy becomes a blind byte-shuffler that takes bytes from the client and sends them to the server and returns the bytes the server replied with back to the client.
I've created a Mulesoft project using the IMAP connector to retrieve e-mail messages. It works fine running locally via Anypoint Studio. When I attempt to deploy it to cloudhub, I get the following error:
Your application has failed with exception com.mulesoft.mmc.agent.v3.dto.DeploymentException: Failed to start inbound endpoint "endpoint.imaps.jwu.platform.gmail.com"
I understand the limitations with inbound connections to cloudhub. My question is this, Is there a way to make use of the IMAP connector on cloudhub? Or am I better off switching over to the POP connector?
Yes IMAP connector can be used in the cloudhub.
The IMAP Connector, which is configurable only as an inbound endpoint (also known as a message source) with a one-way exchange pattern, implements a transport channel that enables your Mule application to retrieve email from an IMAP email server.
IMAP is similar to POP3, except IMAP supports both online and offline modes. For instance, IMAP users can leave email messages on the IMAP server until they explicitly delete them. Like POP3, IMAP cannot send email; for that, you must implement an SMTP outbound endpoint.
For a secure transport channel (either TLS or SSL), you can specify the IMAPS protocol.
Please try this flow I have deployed successfully in cloudhub
<imaps:connector name="IMAP" validateConnections="true" checkFrequency="1" doc:name="IMAP" deleteReadMessages="false">
<imaps:tls-client path="*" storePassword="*"/>
<imaps:tls-trust-store path="*" storePassword="*"/>
</imaps:connector>
<flow name="imapFlow">
<imaps:inbound-endpoint host="imap.gmail.com" port="993" user="example%40gmail.com" password="password" connector-ref="IMAP" responseTimeout="10000" doc:name="IMAP"/>
<logger message="#[payload]##############" level="INFO" doc:name="Logger"/>
</flow>
</mule>
I am implementing XMPP service in the browser using BOSH. I use JAXL library. I am able to manage the connection over BOSH to my localhost server (ejabberd). The session is started and the user is authenticated with no problem. However, when I just change the BOSH host to jappix.com, the very first response from the server is only empty body. Even if I repeat the request (according to XEP-206) I still get only empty body so I'm unable to perform any other actions.
So that's my question: Is it possible to use jappix.com to handle my BOSH requests? Are there any limitations? How can I fix this issue? I'll provide more information if needed.
I am the Jappix.com owner!
Your question does not concern our service directly but more likely a node-xmpp-bosh - the BOSH server we are running - bug (?) that you can report on http://code.google.com/p/node-xmpp-bosh/