I have frequently received many questions from client facing problem when Accessing websites. Sometimes it is just a block but sometimes problem can also be cause by the browser. Below I have a very good indetailed report on the problem faced by client on Firefox browser.
Root Cause Analysis done on client problem
--------------------------------------------------------------
Problem Faced: Client was not able to use chat feature on OLX Website
Browser Used: Firefox
Few things that were identified while addressing these Web Chat Problems that use "WebSocket Protocol(Secure)" via SafeSquid-SWG.
SafeSquid is an HTTP(S) Proxy Server.
"WebSocket Protocol(Secure)" will not work When SSL Inspection is ENABLED on SafeSquid-SWG, Therefore this will result in an error in some web applications as well as desktop applications that use this Protocol and Connect via SafeSquid-SWG(SSL INSPECTION is ENABLED).
Then how can we access these applications?
SafeSquid-SWG provides a Realtime change in configuration, the user/admin can change the SafeSquid-SWG configuration in Realtime the way it suits them Example: Allowing Blocked Websites in realtime without disturbing any other websites session or Restarting the Proxy Server. Coming back to the Solution part: In order to access these Applications, You need to Bypass it from SSL Inspection [Note: If SSL Inspection is Disabled, then anyhow this Blocking problem should not occur until and unless this Application does not use a different Port Not specified in the System Configuration.
The problem was still faced even after the website was added to Bypass SSL Inspection, Why?
After I received the web session the website was already added to an Appropriate Category which is BYPASSED from SSL Inspection. The Website was added to Private Category: "BYPASS SSL" which is Profiled to BYPASS SSL INSPECTION.
The Root Cause Found during the Web Session was related to the Firefox browser problem. The Firefox browser on that machine was not able to use "WebSocket Protocol(Secure)" when Connect via SafeSquid-SWG. Whereas when Chrome Browser was used, the web chat application was accessible and working fine.
Sometimes in order to solve the problem we need to only consider the client setup which in case one of them is the browser used the browser can be an older version which might be having some bug related to such scenario.
Therefore,
I will recommend you all to do check the Web application using both the browser Firefox and Google Chrome.
I have attached a small snapshot of finding such problems using the browser debugging tool.
The console sections prints any kind of connection establishment problems.
- websocketProblemInSamSung.png (147.32 KiB) Viewed 1600 times