Bug #21127
closed
Scap content file is printed into logs
Added by Ondřej Pražák about 7 years ago.
Updated about 6 years ago.
Description
Debug logger logs the response body. When scap content is downloaded via hammer, the response is the file itself, so the entire scap content file ends up in the logs. Because it only clutters the logs and does not contain any relevant debugging information, I think we should skip logging response body for download actions. This goes for tailoring files as well.
Steps to reproduce:
1) Download scap content using hammer/api
Files
Related issues
1 (1 open — 0 closed)
luckily we don't log debug messages in production, I agree we should just silence response body for download actions
- Status changed from New to Ready For Testing
- Assignee set to Ondřej Pražák
- Pull request https://github.com/theforeman/foreman_openscap/pull/357 added
- Target version set to foreman_openscap 0.11.0
- Fixed in Releases foreman_openscap 0.11.0 added
- Status changed from Ready For Testing to Closed
- Bugzilla link set to 1650543
- Bugzilla link deleted (
1650543)
The BZ 1650543 is somehow related but a different bug actually.
- Related to Bug #25482: Excessive logging of OpenScap report via Rails
added
Also available in: Atom
PDF