Wtop

Latest version: v0.7.11

Safety actively analyzes 630130 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 4

0.6.7

==========================

Improved
--------

- Updated to use hashlib instead of md5 (`Google Code Issue 28`_)
- Corrected domain parsing to accept httpS URLs (`Google Code Issue 27`_)
- Added support for `%A` Local IP-Address (`Google Code Issue 26`_)

.. _`Google Code Issue 28`: http://code.google.com/p/wtop/issues/detail?id=28
.. _`Google Code Issue 27`: http://code.google.com/p/wtop/issues/detail?id=27
.. _`Google Code Issue 26`: http://code.google.com/p/wtop/issues/detail?id=26

0.6.6

==========================

Improved
--------

- `%D` microseconds handling fixes
- Fixed python warnings

Deprecated or Known Issues
--------------------------

- Removed curses (`Google Code Issue 23`_)

.. _`Google Code Issue 23`: http://code.google.com/p/wtop/issues/detail?id=23

0.6.3

==========================

Improved
--------

- Added experimental, limited support for Micrsoft IIS logs. At the moment only
the "W3c Extended" format is supported. In a future release there will be
support for custom column layouts, etc. Many thanks to jbowtie for the patch.
(`Google Code Issue 16`_; see `CONTRIBUTORS.rst`_)
- Added transparent support for Apache logfiles created with rotatelogs_. It
should Just Work.
- Curses support in wtop mode, if available.
- Minor cleanups & speedups

.. _`Google Code Issue 16`: http://code.google.com/p/wtop/issues/detail?id=16`
.. _rotatelogs: http://httpd.apache.org/docs/2.0/programs/rotatelogs.html

0.6.1

==========================

Improved
--------

- `--sort LIMIT:FIELD:DIRECTION` option for sorting and limiting aggregate
queries.
- Added long options such as `--output` for `-o` and `--filter` for `-f`.
- Added aggregate functions `var()` (population variance) and `dev()` (standard
deviation)
- Experimental `--x-tmp-dir=/tmp` option when you are running aggregates over
large (> 10 million lines) logs. If you've run out of memory trying to run a
logrep query, try this option. If not, don't use it.
- More cleanups, getting rid of special cases, etc.
- Several speedups, bugfixes, etc.

0.6.0

==========================

Improved
--------

- Added support for aggregate functions `avg()`, `min()`, `max()`, `count(*)`
and `sum()` in grep mode.
- Added `year`, `month`, `day`, `hour` and `minute` fields for output (`-o`)
and filters (`-f`)
- Minor speedups and cleanups.

Deprecated or Known Issues
--------------------------

- The `-g` and `-v` options are deprecated and will be removed in version 1.0
unless there is a general uproar. `-f` filters are more accurate and
generally faster.

0.5.9

==========================

Improved
--------

- Several small bugs.
- Support for Python 2.4. In earlier versions logrep required Python 2.5 or
higher.
- Added a `!~` operator to the `-f FILTER` option. You can now filter out
fields that do not match. For example, to see 'foo.html' hits that were NOT
referred by 'example.com'::

-f 'url~foo.html,ref!~www.example.com'

- Added a 'botname' field: it will show the substring from the user-agent field
it matched to determine that the request came from a robot. You can filter
and output it just like any other.
- Added `-R` option as a shorthand for `-f 'bot=1'`. Shows only traffic that is
probably from a robot and not a human.

Deprecated or Known Issues
--------------------------

- The `-h` option (human traffic only) has been renamed `-H`. `-h` now outputs
the man page.

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.