From 9908232d1bc524e03af0a1f2097f12f218238ec5 Mon Sep 17 00:00:00 2001
From: Daniel Gruno
To keep the thundering herd at bay, the
Once a connection is assigned to handle a particular request, the basic
- request informaton (e.g. HTTP headers, etc) is sent over the connection in
+ request information (e.g. HTTP headers, etc) is sent over the connection in
a highly condensed form (e.g. common strings are encoded as integers).
Details of that format are below in Request Packet Structure. If there is a
body to the request (content-length > 0)
, that is sent in a
@@ -139,7 +139,7 @@ ProxyPassReverse /apps/foo http://www.example.com/foo
been transferred yet. This is necessary because the packets have a fixed
maximum size and arbitrary amounts of data can be included the body of a
request (for uploaded files, for example). (Note: this is unrelated to
- HTTP chunked tranfer).
+ HTTP chunked transfer).
Each message is accompanied by a differently formatted packet of data. @@ -277,7 +277,7 @@ ProxyPassReverse /apps/foo http://www.example.com/foo
To ensure some basic security, the container will only actually do the
Shutdown
if the request comes from the same machine on which
it's hosted.
The first Data
packet is send immediatly after the
+
The first Data
packet is send immediately after the
Forward Request
by the web server.
The servlet container can send the following types of messages to the webserver:
@@ -578,7 +578,7 @@ AJP13_GET_BODY_CHUNK :=The container asks for more data from the request (If the body was
too large to fit in the first packet sent over or when the request is
- chuncked). The server will send a body packet back with an amount of data
+ chunked). The server will send a body packet back with an amount of data
which is the minimum of the request_length
, the maximum send
body size (8186 (8 Kbytes - 6))
, and the number of bytes
actually left to send from the request body.
--
2.40.0