mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 14:48:21 +00:00
Since these now measure "seen" data, set the default to 0.
- A null value no longer fits since if there is no body a value of zero makes sense. Previously, a null value would makes sense because the Content-Length header may not have been sent which would leave the field null.
This commit is contained in:
parent
6db77dc285
commit
c621da523b
1 changed files with 2 additions and 2 deletions
|
@ -32,13 +32,13 @@ export {
|
||||||
user_agent: string &log &optional;
|
user_agent: string &log &optional;
|
||||||
## The actual uncompressed content size of the data transferred from
|
## The actual uncompressed content size of the data transferred from
|
||||||
## the client.
|
## the client.
|
||||||
request_body_len: count &log &optional;
|
request_body_len: count &log &default=0;
|
||||||
## This indicates whether or not there was an interruption while the
|
## This indicates whether or not there was an interruption while the
|
||||||
## request body was being sent.
|
## request body was being sent.
|
||||||
request_body_interrupted: bool &log &default=F;
|
request_body_interrupted: bool &log &default=F;
|
||||||
## The actual uncompressed content size of the data transferred from
|
## The actual uncompressed content size of the data transferred from
|
||||||
## the server.
|
## the server.
|
||||||
response_body_len: count &log &optional;
|
response_body_len: count &log &default=0;
|
||||||
## This indicates whether or not there was an interruption while the
|
## This indicates whether or not there was an interruption while the
|
||||||
## request body was being sent. An interruption could cause hash
|
## request body was being sent. An interruption could cause hash
|
||||||
## calculation to fail and a number of other problems since the
|
## calculation to fail and a number of other problems since the
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue