mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-22 12:30:07 +00:00
CLEANUP: assorted typo fixes in the code and comments
This is 19th iteration of typo fixes
This commit is contained in:
parent
7b00e31509
commit
d7a988c14a
@ -296,7 +296,7 @@ instances attached to a stream :
|
||||
unsigned short flags; /* STRM_FL_* */
|
||||
unsigned char nb_req_data_filters; /* Number of data filters registered on the request channel */
|
||||
unsigned char nb_rsp_data_filters; /* Number of data filters registered on the response channel */
|
||||
unsigned long long offset[2]; /* gloal offset of input data already filtered for a specific channle
|
||||
unsigned long long offset[2]; /* gloal offset of input data already filtered for a specific channel
|
||||
* 0: request channel, 1: response channel */
|
||||
};
|
||||
|
||||
@ -628,7 +628,7 @@ For instance :
|
||||
/* ... */
|
||||
}
|
||||
|
||||
Finally, it may be interesting to notifiy the filter when the stream is woken up
|
||||
Finally, it may be interesting to notify the filter when the stream is woken up
|
||||
because of an expired timer. This could let a chance to check some internal
|
||||
timeouts, if any. To do so the following callback must be used :
|
||||
|
||||
@ -709,7 +709,7 @@ instance :
|
||||
'include/haproxy/channels-t.h'.
|
||||
|
||||
* 'chn' is the channel on which the analyzing is done. It is possible to
|
||||
dertermine if it is the request or the response channel by testing if
|
||||
determine if it is the request or the response channel by testing if
|
||||
CF_ISRESP flag is set :
|
||||
|
||||
│ ((chn->flags & CF_ISRESP) == CF_ISRESP)
|
||||
@ -986,7 +986,7 @@ available data (available from its point of view), blocking the data forwarding.
|
||||
Internally, filters own 2 offsets representing the number of bytes already
|
||||
analyzed in the available input data, one per channel. There is also an offset
|
||||
couple at the stream level, in the strm_flt object, representing the total
|
||||
number of bytes already forwarded. These offsets may be retrived and updated
|
||||
number of bytes already forwarded. These offsets may be retrieved and updated
|
||||
using following macros :
|
||||
|
||||
* FLT_OFF(flt, chn)
|
||||
@ -1180,7 +1180,7 @@ update data itself, i.e. the buffer offsets, using following function :
|
||||
|
||||
* 'flt_update_offsets()' : This function must be called when a filter alter
|
||||
incoming data. It updates offsets of the stream and of all filters
|
||||
preceeding the calling one. Do not call this function when a filter change
|
||||
preceding the calling one. Do not call this function when a filter change
|
||||
the size of incoming data leads to an undefined behavior.
|
||||
|
||||
A good example of filter changing the data size is the HTTP compression filter.
|
||||
|
@ -216,7 +216,7 @@ tunneled data. But tunneled data will never be mixed with message data to avoid
|
||||
ambiguities. Thus once the flag marking the end of the message is set, it is
|
||||
easy to know the message ends. The end is reached if the HTX message is empty or
|
||||
on the tail HTX block in the HTX message. Once all blocks of the HTX message are
|
||||
consumed, tunneled data, if any, may be transfered.
|
||||
consumed, tunneled data, if any, may be transferred.
|
||||
|
||||
|
||||
3.1. The start-line
|
||||
@ -519,8 +519,8 @@ block :
|
||||
pointing on the block payload is returned.
|
||||
|
||||
- htx_is_unique_blk() may be used to know if a block is the only one
|
||||
remaining inside an HTX message, excluding unsued blocks. This function is
|
||||
pretty useful to determine the end of a HTX message, in conjonction with
|
||||
remaining inside an HTX message, excluding unused blocks. This function is
|
||||
pretty useful to determine the end of a HTX message, in conjunction with
|
||||
HTX_FL_EOM flag.
|
||||
|
||||
4.7. Advanced functions
|
||||
|
@ -3102,7 +3102,7 @@ spoe_check(struct proxy *px, struct flt_conf *fconf)
|
||||
|
||||
if (!sink || sink->type != SINK_TYPE_BUFFER) {
|
||||
ha_alert("Proxy %s : log server used by SPOE agent '%s' declared"
|
||||
" at %s:%d uses unkown ring named '%s'.\n",
|
||||
" at %s:%d uses unknown ring named '%s'.\n",
|
||||
px->id, conf->agent->id, conf->agent->conf.file,
|
||||
conf->agent->conf.line, logsrv->ring_name);
|
||||
return 1;
|
||||
|
@ -881,7 +881,7 @@ void apply_server_state(void)
|
||||
if (local_vsn)
|
||||
srv_state_px_update(curproxy, local_vsn, &local_state_tree);
|
||||
|
||||
/* Remove unsused server-state lines */
|
||||
/* Remove unused server-state lines */
|
||||
node = eb64_first(&local_state_tree);
|
||||
while (node) {
|
||||
st_line = eb64_entry(node, typeof(*st_line), node);
|
||||
|
Loading…
Reference in New Issue
Block a user