JOH |
|
Jabber Over HTTP Tunnel |
Sergey Poznyakoff |
JOH User Manual (split by node): | ? |
There are two most common scenarios for configuring Jabber Over HTTP proxy.
In the first scenario, you have a dedicated Jabber server and the port
80 (HTTP) is not used on that server. In this case you will use
standalone mode. In this mode johd
is configured
to listen on port 80 to proxy incoming requests to your
Jabber server and vice-versa.
In the second scenario, the port 80 is already in use by an HTTP
server running on the same box as your Jabber server. For such
cases, JOH provides a CGI mode. In this mode, you start
johd
to listen on an auxiliary port, and configure your
HTTP server to run a CGI program, joh.cgi
, which is included
in the package. The system then works as follows. HTTP polling
requests are received by your HTTP server, which invokes
joh.cgi
to handle them, In its turn, joh.cgi
extracts the necessary data from each request, reformats it and sends
it over to the johd
daemon over the auxiliary port. When
a subsequent request arrives, joh.cgi
receives the reply from
johd
, formats it as a HTTP response and sends it back to the
HTTP server, which sends it to the requesting client.
The CGI mode works only with HTTP Polling.
Of course, there may be combined cases, e.g.:
joh.cgi
would be installed on the HTTP server and johd
on the
Jabber server.
johd
in standalone mode on this machine
and configure it to communicate with your main Jabber server.
JOH User Manual (split by node): | ? |
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.