✨ feat(envoy-proxy): Enable access logging for HTTP requests #68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HTTP request logging
Goal
We want to be able to better track what has happened (and when). This PR enables us to do just that - access logs are written to stdout.
Example: Command injection (via proxy-service)
Command executed:
$ ug-exploit cmd-inject-proxy "echo test"
The envoy-proxy logs can then for example be retrieved as follows:
Matching log line (formatted for better readability):
As can be seen in the log line above, the command we've attempted to inject (
echo test
) has been logged as well as the time stamp, the content type of the request etc.