Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 46228 invoked from network); 1 Feb 2002 14:29:59 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Feb 2002 14:29:59 -0000 Received: (qmail 2102 invoked by uid 97); 1 Feb 2002 14:29:48 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 2078 invoked by uid 97); 1 Feb 2002 14:29:47 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 2060 invoked by uid 97); 1 Feb 2002 14:29:46 -0000 Date: 1 Feb 2002 14:29:30 -0000 Message-ID: <20020201142930.26789.qmail@icarus.apache.org> From: jfclere@apache.org To: jakarta-tomcat-connectors-cvs@apache.org Subject: cvs commit: jakarta-tomcat-connectors/webapp/docs warp.html X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N jfclere 02/02/01 06:29:30 Modified: webapp/docs warp.html Log: Add the missing part of the document. Revision Changes Path 1.5 +162 -13 jakarta-tomcat-connectors/webapp/docs/warp.html Index: warp.html =================================================================== RCS file: /home/cvs/jakarta-tomcat-connectors/webapp/docs/warp.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- warp.html 28 Jan 2002 16:27:21 -0000 1.4 +++ warp.html 1 Feb 2002 14:29:30 -0000 1.5 @@ -200,8 +200,7 @@ Client Server -One end of the peer notifies -the other of a fatal connection error +One end of the peer notifies the other of a fatal connection error N/A @@ -213,8 +212,8 @@ Client Server -One end of the peer notifies -the other that the connections is going to be closed +One end of the peer notifies the other that the connections is going +to be closed N/A @@ -224,7 +223,8 @@ 0xff - Client
Serve +Client  +
Serve  A protocol error occourred, the connection must be closed. @@ -687,8 +687,7 @@
  • [integer] The server unique-id.
    • - -


    CONF_DEPLOY 0x05 +CONF_DEPLOY 0x05
    The client attempts to deploy a web application.

    • @@ -713,8 +712,7 @@
    •  [string] The web application real path (where it's expanded).
    - -


    CONF_MAP 0x07 +CONF_MAP 0x07
    The client requests to the server to enumerate all mappings for a specified web-application. The server replies to this message with a serie of MAP_ALLOW and MAP_DENY packets, terminated by a MAP_DONE packet. @@ -730,8 +728,7 @@

  •  [string] An url-pattern as defined by the Servlet specification.
    • - -


    CONF_MAP_DENY 0x09 +CONF_MAP_DENY 0x09
    The server replies to a CONF_MAP message with those packets to indicate a mapping to a resource that must be served by the server (servlet container).

      @@ -747,8 +744,160 @@

      CONF_PROCEED 0x0f
      Server issues this message in response to a CONF_DONE message, to acknowledge its readiness to accept requests. -
        -
        +

      REQ_INIT 0x10 +
      The client requests to the WARP server that a request is about to be +processed. +

        +
      • + [integer] The web-application unique ID for this server. (From the +CONF_MAP).
        • + +
      • +[string] The HTTP method used for this request.
        • + +
      • +[string] The request URI.
        • + +
      • +[string] The request query arguments.
        • + +
      • +[string] The request protocol (HTTP/1.0, HTTP/1.1...).
        • +
      +REQ_CONTENT 0x11 +
      The mime content type and length of this request. +
        +
      • +[string] The MIME content type of this reques.
        • + +
      • +[integer] The content length of this request.
        • +
      +REQ_SCHEME 0x12 +
      The scheme description of this request. +
        +
      • +[string] The scheme (part before :// in the URL) of this request.
        • +
      +REQ_AUTH 0x13 +
      Authentication information of the HTTP remote peer. +
        +
      • +[string] The remote-user name.
        • + +
      • +[string] The authentication information.
        • +
      +REQ_HEADER 0x14 +
      An HTTP request header. There are severals. +
        +
      • +[string] The header name.
        • + +
      • +[string] The header value.
        • +
      +REQ_SERVER 0x15 +
      The HTTP server information. +
        +
      • +[string] The HTTP server host name.
        • + +
      • +[string] The HTTP server IP address.
        • + +
      • +[ushort] The port receiving the HTTP request.
        • +
      +REQ_CLIENT 0x16 +
      The HTTP client (remote peer) information. +
        +
      • +[string] The HTTP client host name.
        • + +
      • +[string] The HTTP client IP address.
        • + +
      • +[ushort] The remote port originating the HTTP request.
        • +
      +REQ_PROCEED 0x1f +
      The client finished transmitting the request. The server can now proceed +and process the request. +

      ASK_SSL 0x43 +
      The WARP server (Tomcat) asks the WARP client to transfer the basic +SSL information (cypher, keysize and session). +

      ASK_SSL_CLIENT 0x44 +
      The WARP server (Tomcat) asks the WARP server to transfer the client +certificate.  (just the first element of the chain and the webserver +should request for it to the browser if possible). +

      REP_SSL_CERT 0x52 +
      The client certificate (remote peer). +

        +
      • +[string] The client certificate. (PEM format).
        • +
      +REP_SSL 0x53 +
      SSL information. +
        +
      • +[string] The cipher_suite.
        • + +
      • +[string] The ssl session. (That is not in the spec's).
        • + +
      • +[ushort] size of the algorithm (56-128).
        • +
      +REP_SSL_NO 0x5F +
      The requested SSL information is not available. +

      CBK_READ 0x40 +
      A request callback. The WARP server queries the WARP client  (HTTP +server) to transmit a chunk of the request body. +

        +
      • +[ushort] The max number of bytes the server is able to receive.
        • +
      +CBK_DATA 0x41 +
      As requested by the WARP server, the WARP client (HTTP server) transmits +a chunk of the request body. +
        +
      • +[raw] A chunk of the request body.
        • +
      +CBK_DONE 0x42 +
      The WARP client (HTTP server) informs the WARP server that the request +body has been fully transmitted. +

      RES_STATUS 0x20 +
      The server replies with the HTTP response status for the request. +

        +
      • +[ushort] The HTTP status of the response.
        • + +
      • +[string] The HTTP response message.
        • +
      +RES_HEADER 0x21 +
      An HTTP MIME response header to send to the client. There are severals +of these. +
        +
      • +[string] The MIME header name.
        • + +
      • +[string] The MIME header value.
        • +
      +RES_COMMIT 0x2f +
      The server indicates that the first part of the response (HTTP status +line and MIME headers) are to be committed to the client (remote peer). +

      RES_BODY 0x30 +
      The HTTP response body. +

        +
      • +[raw] A chunk of the response body. Up to 65535 bytes.
        • +
      +RES_DONE 0x3f +
      The server finished transmitting the response.
       
        -- To unsubscribe, e-mail: For additional commands, e-mail: