Free rpc over http software for linux

Socks via HTTP provides a socks tunnel via HTTP.

Socks via HTTP is a program converting SOCKS requests into HTTP requests and tunnelling them through HTTP proxies if needed.

The SOCKS protocol allows programs to traverse firewalls on any port number and is used by many popular programs, like Napster, MSN Messenger, CRT(telnet client) and many others.

Many companies restrict firewall traversals only to HTTP requests, disabling SOCKS proxy.

Socks via HTTP provides a miniature SOCKS server for the SOCKS client, performing its connection through an HTTP proxy to a remote server, which establishes the real connection.

Socks via HTTP is 100% Java, and can run on any OS. It is entirely written in Java.

POE::Component::Server::HTTP is a foundation of a POE HTTP Daemon.

SYNOPSIS

use POE::Component::Server::HTTP;
use HTTP::Status;
my $aliases = POE::Component::Server::HTTP->new(
Port => 8000,
ContentHandler => {
/ => &handler1,
/dir/ => sub { ... },
/file => sub { ... }
},
Headers => { Server => My Server },
);

sub handler {
my ($request, $response) = @_;
$response->code(RC_OK);
$response->content("Hi, you fetched ". $request->uri);
return RC_OK;
}

POE::Kernel->call($aliases->{httpd}, "shutdown");
# next line isnt really needed
POE::Kernel->call($aliases->{tcp}, "shutdown");

POE::Component::Server::HTTP (PoCo::HTTPD) is a framework for building custom HTTP servers based on POE. It is loosely modeled on the ideas of apache and the mod_perl/Apache module.

It is built alot on work done by Gisle Aas on HTTP::* modules and the URI module which are subclassed.

PoCo::HTTPD lets you register different handler, stacked by directory that will be run during the cause of the request.

Jabber::RPC::HTTPgate is an HTTP gateway for Jabber-RPC / XML-RPC.

SYNOPSIS

use Jabber::RPC::HTTPgate;

my $gw = new Jabber::RPC::HTTPgate(
server => myserver.org:5701,
identauth => jrpchttp.localhost:secret,
httpcomp => http,
);

$gw->start;

Jabber::RPC::HTTPgate is an experimental gateway that provides a conduit service between traditional (HTTP-transported) XML-RPC encoded requests/responses and Jabber-RPC (XML-RPC encoded requests/responses transported over Jabber).

The idea is that you can start a gateway, that connects as a component to the backbone of a Jabber server, and it proxies Jabber-RPC to HTTP-based XML-RPC endpoints, and vice versa. That means that your Jabber-RPC client can not only make XML-RPC encoded calls to a Jabber-RPC endpoint but also to a traditional HTTP-based XML-RPC endpoint. And it also means that your traditional HTTP-based XML-RPC client can make XML-RPC encoded calls to a Jabber-RPC endpoint.

Jabber -> HTTP

When you create and start up a gateway, it listens for Jabber-RPC calls, just like a normal Jabber-RPC responder. On receipt of such a call, the gateway creates an HTTP request and sends this request on to the HTTP-based XML-RPC endpoint. The response received back from this HTTP call is relayed back to the original Jabber-RPC requester.
While a Jabber-RPC endpoint address is a Jabber ID (JID), an traditional XML-RPC endpoint address is a URL. So all the Jabber-RPC client needs to do is specify the URL in the resource part of the gateways endpoint JID.

HTTP -> Jabber

As well as listening for Jabber-RPC calls, a gateway will also service incoming HTTP requests that can be made to the HTTP component that this gateway uses. The HTTP component (called simply http) can be downloaded from the normal Jabber software repository.

On receipt of an HTTP request (passed to it by the HTTP component), the gateway creates a Jabber-RPC request containing the XML-RPC encoded payload, and sends it on to the Jabber-RPC responder endpoint. This endpoint is identified (via a JID) by the path part of the URL used in the call by the traditional client.

XML-RPC project is a lightweight standard, enabling RPC over HTTP by using XML as a marshaling format.

REBOL project is a scripting language (architected mainly by Carl Sassenrath of Amiga fame).

rebXR brings these two great flavors together, making REBOL a first-class citizen of XML-RPC land.

The Apache HTTP Server Project is an effort to develop and maintain an open-source HTTP server for modern operating systems including UNIX and Windows NT. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP services in sync with the current HTTP standards.
Apache has been the most popular web server on the Internet since April of 1996. The May 2003 Netcraft Web Server Survey found that 62% of the web sites on the Internet are using Apache, thus making it more widely used than all other web servers combined.
The Apache HTTP Server is a project of the Apache Software Foundation.

CamRPC is a simple client/server solution to update/manage several webcams using a PHP enabled Web server and any client with XML-RPC capabilities.
Enhancements:
Server
- A web server (Apache tested, http://httpd.apache.org/)
- PHP 4 >= 4.1.0 with XML module
- php XML-RPC (http://xmlrpc.usefulinc.com/, included 1.1.1 in the package)
- A directory with write enabled for the httpd daemon
Client
- Your image grabber of choice
- Python client: python 2 >= 2.2
- Perl client: Frontier::RPC, MIME::Base64 and MIME::Types
Enhancements:
- updated included xml-rpc lib due SA15852: http://secunia.com/advisories/15852/
- Now camrpc is distributed with xml-rpc 1.1.1.

XML-RPC Client/Server C Library is a cross-platform software written in C that supports persistent HTTP/1.1 conenctions over SSL and comes with XML-RPC interface description language and client/server code compiler. Libxr depends on glib2 and libxml2.
Main features:
- Persistent connections over HTTP/1.1
- SSLv3/TLSv1 using OpenSSL.
- XML-RPC interface description language (XDL).
- XML-RPC client stubs/servlet skels compiler.
- Multiple servlets per server.
- Servlet lifetime (init -- call -- call -- fini).
- Multiplatform (linux, mingw32 on windows).
- IPV6 as soon as OpenSSL 0.9.9 is released.

SYNOPSIS

use DCE::RPC; use Authen::Perl::NTLM qw(lm_hash nt_hash);
use constant DCOM_IREMOTEACTIVATION => pack("H32", "B84A9F4D1C7DCF11861E0020AF6E7C57");
use constant DCOM_IF_VERSION => 0x00;
use constant DCOM_XFER_SYNTAX => pack("H32", "045D888AEB1CC9119FE808002B104860");
use constant DCOM_XFER_SYNTAX_VERSION => 0x02;

$passwd = "passwd";
$lm_hpw = lm_hash($passwd);
$nt_hpw = nt_hash($passwd);
$ntlm = new_client Authen::Perl::NTLM($lm_hpw, nt_hpw);
$rpc_host = "www.rpc.com";
$rpc_port = 135;
$rpc = new DCE::RPC($rpc_host, $rpc_port, $ntlm);
$bind_msg = $rpc->rpc_bind_ack_resp(1, DCOM_IREMOTEACTIVATION, DCOM_IF_VERSION,
({interface => DCOM_XFER_SYNTAX, version => DCOM_XFER_SYNTAX_VERSION}));
$request_msg = $rpc->rpc_co_request("Hi, there! This is Stub!", 1, 0x0e, DCOM_IREMOTEACTIVATION, "Authentication Credentials");
$response_msg = $rpc->rpc_request_response($request_msg);
$alt_ctx_msg = $rpc->rpc_alt_ctx(1, DCOM_IREMOTEACTIVATION . DCOM_IF_VERSION
,
({interface => DCOM_XFER_SYNTAX, version => DCOM_XFER_SYNTAX_VERSION}));

The DCE RPC protocol is an application level protocol from OpenGroup that allows applications to do Remote Procedure Calls. It is the underlying wire protocol for DCOM (Distributed Common Object Model) by Microsoft.
This module was motivated by an reverse-engineering effort on a DCOM client. Therefore, functions that are implemented gear more toward client side implementation. Also, the initial version only supports Connection Oriented version of DCE RPC. It also assumes NTLMSSP as the underlying authentication protocol. This can change based on the input of the users of this modules.