[CLEANUP] renamed several HTTP structures
Some parts of HTTP processing were incorrectly called "request" while
they are messages or transactions. The following structure members
have changed :
http_msg.hdr_state => msg_state
http_msg.sor => som
http_req.req_state => removed
http_req => http_txn
diff --git a/doc/internals/http-parsing.txt b/doc/internals/http-parsing.txt
index 7e731c8..fd41b6e 100644
--- a/doc/internals/http-parsing.txt
+++ b/doc/internals/http-parsing.txt
@@ -223,17 +223,17 @@
without optimal support for HTTP pipelining will have the client buffers tied
to the http_session. It may be possible that it is not sufficient for full
pipelining, but this will need further study. The link from the buffers to
- the backend should be managed by the http_request, provided that they are
- serialized. Each http_session, has 0 to N http_requests. Each http_request
- belongs to one and only one http_session.
+ the backend should be managed by the http transaction (http_txn), provided
+ that they are serialized. Each http_session, has 0 to N http_txn. Each
+ http_txn belongs to one and only one http_session.
-- each http_request has 1 request message, and 0 or 1 response message. Each of
- them has 1 and only one http_request. An http_request holds informations such
- as the HTTP method, the URI, the HTTP version, the transfer-encoding, the
- HTTP status, the authorization, the req and resp content-length, the timers,
- logs, etc... The backend and server which process the request are also known
- from the http_request.
+- each http_txn has 1 request message (http_req), and 0 or 1 response message
+ (http_rtr). Each of them has 1 and only one http_txn. An http_txn holds
+ informations such as the HTTP method, the URI, the HTTP version, the
+ transfer-encoding, the HTTP status, the authorization, the req and rtr
+ content-length, the timers, logs, etc... The backend and server which process
+ the request are also known from the http_txn.
- both request and response messages hold header and parsing informations, such
- as the parsing state, start of headers, start of request, captures, etc...
+ as the parsing state, start of headers, start of message, captures, etc...