I am personally have come across a lot of scenarios where the problem faced by the client is very basic one, but the error thrown or shown by SafeSquid makes it complex for the end users as well as the clients also sometimes due to lack of real-time error reporting a simple AJAX call made by the browser to fetch or sync data inside the windows results in bad user experience.
Let's understand what are the possible problem that can be faced
1. Website is accessible but few things like chat, incomplete data display ( SITE HAVING BROKEN DISPLAY ) or in other words site not serving the purpose etc are creating the problem.
NOTE: site not serving the purpose can include site's button is not working, sites images are not loaded, site is not structured properly etc.
2. Website is showing a block template.
3. Website is accessible but not able to login to that website.
4. Website is accessible but multimedia contents are not working on that site.
Note: Few SafeSquid Blocked Templates are not user friendly ( they are less explanative ) , it does not explains the actual problem properly which results in complications and high resolution time.
The above problems faced by clients needs proper debugging and root cause analysis before we actually solve it
This can be very easily solved by customer technician itself just by opening the browser based debugging tool in the clients end.
Major of the problems are displayed in the debugging tool itself.
------------------------------------------------------------
1. The Console Tab of the Debugging Tool.
------------------------------------------------------------
A) The console window will display many errors
Which include error in javascript due to AJAX or request call failure .
B) the console windows display any connection established error and over there if any website is blocked then the complete Request with protocol, domain name , port number are displayed.
Which helps to identify the root cause.
A quick example of a Samsung chat feature blocked because it was using Secure WebSocket Protocol (wss)
Below is the console log.
- websocketProblemInSamSung.png (147.32 KiB) Viewed 1236 times
2. The Network Tab of the Debugging Tool.
------------------------------------------------------------
A) The network tab will display all the request made by that particular web application with details like
a) Request Domain Port
b) Remote Server
c) Status Code
d) Request Headers
e) Request Body
f) Response Headers
g) Response Body
h) Time Taken
ETC And other debugging info.
These information help us understand the root cause of the problem.
Example: if the status code is 403 with SafeSquid-SWG response headers x-template as blocked then the website is blocked by the SafeSquid-SWG
Below is the Debugging Headers provided by SafeSquid for each Request made by the client
The debug headers include details about
1. The Client ID that the particular Connection Request has.
2. UserGroup the user fall in.
3. Applied RequestTypes, ResponseTypes, Policy
Etc as shown below.
In the below screenshot it displays the response headers send to the client by SafeSquid which contains X-SAFESQUID in the beginning of Response header fields are Debugging Headers provided by SafeSquid
They provide detailed information about that Request and Policies applied for that Request like
1. Cookie Filter
2. Image Filter
3. Text Filter
Etc and other filters even if they are enabled or disabled.
- IMG-20200502-WA0006.jpg (70.03 KiB) Viewed 1236 times
Note:
SafeSquid Provides alot of debugging headers attached to the client response headers
These headers are further explained in an other post.please once go through to get detailed information.
B) Many Connection related details or block are not displayed by the network tab therefore we require the console tab as well to understand the problem properly.
The Debugging Tool makes the debugging very easy for the customer as well as for us and reduces alot of efforts and time.