Skip to content

doc: upgrade guide for logging http custom headers #8978

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
catenacyber wants to merge 2 commits into from
Closed

doc: upgrade guide for logging http custom headers #8978

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d1ee18c
doc: upgrade guide for logging http custom headers
catenacyber Jun 6, 2023
7784f15
Update doc/userguide/upgrade.rst
catenacyber Jun 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions doc/userguide/upgrade.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,9 @@ Logging changes
- Protocol values and their names are built into Suricata instead of using the system's ``/etc/protocols`` file. Some names and casing may have changed
in the values ``proto`` in ``eve.json`` log entries and other logs containing protocol names and values.
See https://redmine.openinfosecfoundation.org/issues/4267 for more information.
- Custom logging of HTTP headers via suricata.yaml ``outputs.eve-log.types.http.custom``
is now done in subobjects ``response_headers`` or ``request_headers`` (as for option ``dump-all-headers``)
instead than at the root of the ``http`` json object (avoids some collisions).
Comment thread
catenacyber marked this conversation as resolved.
Outdated

Deprecations
~~~~~~~~~~~~
Expand Down