You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Personally, I mostly use tf on apache https access_log files and have used the default space-separation. This mostly works, but sometimes not, see the two following lines:
In the first one, the target URL is (space-separated) field number 7. In the second one, which I believe represents someone connecting to the server and not doing anything till it times out, there is no HTTP verb and field 7 is the HTTP status signaling timeout.
If topfew could recognize quoted fields, then field 6 in the first example would be GET /ongoing/ongoing.atom and in the second would be -, which would be more correct from the point of topfew processing. So I think there needs to be a -q option, or some such, to ask topfew to process quote-delimited space-separated fields properly.
The text was updated successfully, but these errors were encountered:
* kaizen: add -q option for quoted fields
addresses #28 and #27
Signed-off-by: Tim Bray <tbray@textuality.com>
* add missing test data
Signed-off-by: Tim Bray <tbray@textuality.com>
---------
Signed-off-by: Tim Bray <tbray@textuality.com>
Personally, I mostly use tf on apache https access_log files and have used the default space-separation. This mostly works, but sometimes not, see the two following lines:
In the first one, the target URL is (space-separated) field number 7. In the second one, which I believe represents someone connecting to the server and not doing anything till it times out, there is no HTTP verb and field 7 is the HTTP status signaling timeout.
If topfew could recognize quoted fields, then field 6 in the first example would be
GET /ongoing/ongoing.atom
and in the second would be-
, which would be more correct from the point of topfew processing. So I think there needs to be a-q
option, or some such, to ask topfew to process quote-delimited space-separated fields properly.The text was updated successfully, but these errors were encountered: