-
Notifications
You must be signed in to change notification settings - Fork 103
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.
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
Block all is not logged #46
Comments
For very verbose debug logs, including such block logs, you should enable the DEBUG_PROXY switch in Mk.main.mk, recompile, and start sslproxy with the |
I compiled with DEBUG_PROXY and run with -D4. connection.log is empty while conntent.log have content.
debug log
|
They are in the logs you have posted, search for "Applying deferred block action". |
Is it only written to the debug log? |
Yes |
Do you have plan for separate log for blocked sites and passthrough when run with -P ? |
I guess it's not difficult, but I should think about it in detail. |
That would be very useful for debugging and traffic monitoring. |
I have filter rule
Block from ip * to ip * log *
and while traffic has been blocked i don't see that in logs. Below i send debug log where we see only SSL negotiation and connection to destination host without information about from connection from who initialized and information about block action.The text was updated successfully, but these errors were encountered: