But getting complete connection details just by navigating native logs is not possible, because the logs are written in real time as the connections are made.
For example, if you are requesting https://www.google.com and https://mail.google.com then log will be not written on the basis of connection, but on the basis of how the endpoint server response, which means you’ll need to hunt for complete connection details.
Getting complete connection log in a corporate network where they have hundreds of users is an impossible task and can lead to incomplete analysis for the problem.
find_client_id.sh can be used to get complete connection details.
Using the client id from logs will provide complete connection details.
Below are steps on how to use find_client_id.sh
To use find_client_id.sh you are first required to get your connection’s client id.
Client id can be extracted from the response headers section in browsers network tab.
(Note: we are assuming that you know how to open developer tools in a browser)
Also, client id can be extracted from SafeSquid’s native logs Now using the client id, you can get complete connection details.
In your proxy server execute below command
Code: Select all
find_client_id.sh <client id of the connection> | less
safesquid.log is symbolic or soft link to the latest log file generated in native folder.
In case you need to get the output for find_client_id.sh from an old log files, use below find_client_id.sh syntax.
Code: Select all
find_client_id.sh <client id of the connection> <log file to use> | less
To save the output of find_client_id.sh to a file, use redirection.
Code: Select all
find_client_id.sh <client id of the connection> > find_client_id_<client_id>_output.txt
Code: Select all
find_client_id.sh <client id of the connection> <log file to use> > find_client_id_<client_id>_output.txt