Draft Specs


So far, there are two relevant specifications being developed as part of ReverseHttp.


The specification is here.


“This document describes a dynamic, ReST-style means of enrolment and participation in an HTTP network. The message/http and application/http MIME types defined by RFC 2616 are used to build a dynamically-configurable “Remote CGI” service.

“Joining the World Wide Web as an HTTP server has been an ad-hoc, manual process. By using the protocol defined here, programs can provide services to the Web just as easily as they request services from the Web.”


The specification is here.


“This document describes a protocol for tunnelling HTTP traffic over HTTP, with the goal of providing portable, general, securable access to the World Wide Web for programs running in restricted environments, including Javascript programs running in browsers.

“The defined protocol is similar to the widely used HTTP proxying protocol, but differs in that the proxied traffic is carried over an ordinary HTTP connection; the special syntax used by an HTTP proxy is avoided here.”

General considerations when tunnelling HTTP

HTTP is defined to run over reliable, in-order, connected, bidirectional byte-stream transports, such as TCP, by RFC 2616. It depends on the underlying transport in a few different ways:

In other words, HTTP relies on the underlying transport to provide

To generalize HTTP to run over a different transport protocol, these features need to be provided in the new setting.