Mercurial > prosody-modules
view mod_tcpproxy/web/demo.html @ 4629:0e60ce83205c
mod_s2s_keepalive: Ignore errors from the local server
If a stanza can't be delivered and instead an bounce is generated, the
origin of the error, when different from the stanza 'from' should be
indicated in the 'by' attribute of the <error>, which we look for here
so this doesn't count as a successful ping.
An error that does come from the remote means we have connectivity, but
probably no XEP-0199 handling. This is fine. We care about connectivity,
not protocol.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Wed, 21 Jul 2021 15:57:13 +0200 |
parents | 7dbde05b48a9 |
children |
line wrap: on
line source
<html> <head> <script type="text/javascript" src="xmpp.io.js"></script> <script type="text/javascript" src="strophe.js"></script> <script type="text/javascript" src="src/jquery-1.4.2.min.js"></script> <script type="text/javascript"> function handle_connection_status(status, err) { console.log("XMPP status: "+Strophe.Status.CONNECTED); if(status == Strophe.Status.CONNECTED) { var conn = new XMPPIO(xmppconn, "tcp.localhost"); conn.addListener("connect", function () { var req = "GET / HTTP/1.0\r\nHost: example.com\r\n\r\n"; console.log("Sending request: "+req); conn.write(req); }); conn.addListener("data", function (data) { $("<div/>").text(data).appendTo("body"); }); console.log("Connecting to example.com:80..."); conn.connect("example.com", 80); } } var xmppconn = new Strophe.Connection("/http-bind"); xmppconn.connect("anon.localhost", null, handle_connection_status, 50); </script> </head> <body> </body> </html>