In this post I will be highlighting a very important feature of SafeSquid-SWG that reduces debugging problem to a greater extend.
The problem that we see once we deploy any application is the troubleshooting part i.e if any problem is faced due to the application, the application support team comes into the picture and analysis the problem using different log files containing debug information.
This is a SOP for any application.
Same ways SafeSquid-SWG being one of such Application which requires Debugging to understand the root cause of the problem faced.
When a user faces a problem like site is not working as desired or site breaks when using SafeSquid-SWG ( or by any SafeSquid Policy )
We need to do the following things
1. Identify the Problem
2. Understand the Risk of the Problem
3. Apply The Necessary Solution.
For more detail on this follow the below link
******* Identifying Root Cause of the Problem Link ********
The very first step in this is to identify the problem which require use to go through the SafeSquid's log file and track down the appropriate logs which belongs to that web application.
Doing this in a Heavily Loaded SafeSquid Instance is very hard. As it will consume a lot of efforts and time resulting in bad user experience.
Also to actually trace down all the web requests made by that web application is very hard and time consuming in such a heavily loaded system regardless of having the client/machines ip for filtering the results.
SafeSquid has a lot of advance filters which are used to control such Web 2.0 Application and to identify exactly which SafeSquid's filter is breaking a websites functionality is very hard to trace and replicate.
There we need a more convenient and easy solution which can be used by the Application Support Engineers as well as by the SafeSquid instance maintainers to easily and quickly debug such problems.
Below we provide a advabce solution which is very handy and helpful in such scenarios.
------------------------------------------
SIMPLE & QUICK ANSWER
------------------------------------------
SafeSquid-SWG provides an easy way to troubleshoot such problems.
SafeSquid-SWG provides most of the debugging information in the response headers itself , which makes it easy for debugging.
Information includes the Policy that were applied to that request becuase of the respective use case.
-----------------------------------
INDETAILED ANSWER
-----------------------------------
Now-a-days, Every Browser provides a built-in debugging tool. Which makes it easy for any web application developer to debug the web application easily on the browser itself.
The debugging tool in the browser provides different section which have different information and stats.
It contains
1. Elements
2. Console
3. Source
4. Network
5. Performance
6. Memory
7. Application
8. Security
9. Audit
These different tabs provides different information.
The section that are very helpful are :
1. Console
-------------------
This Section provides good debugging for the web application like error in function , error in network call, web developers add more information that are displayed here for debugging, it also provides information when their is Connection establishment problem which detailed info like protocol, domain name, port number, url path, search query etc.
This help us identify if any website is getting block due to any restriction via SafeSquid-SWG.
Some of the Request which face connection establishment problem are not listed in network tab we need to go to the Console tab to get the details about the connection problem.
A Quick Console Tab related Debugging info is shown in the below snapshot.
Which explains that connection to a domain failed with details
- websocketProblemInSamSung.png (147.32 KiB) Viewed 1674 times
-------------------
This section provides information related to the SSL part i.e the certificate details in a more informative format.it provides details like
1. Encryption Algorithm Used.
2. Certificate Validity.
This section is important to understand any problem related to SSL.
The below 2 snapshots shows Information provided by the Security Section
- chromeDevToolSecuritySection.png (65.61 KiB) Viewed 1674 times
- chromeDevToolSecuritySection_origindetails.png (100.85 KiB) Viewed 1674 times