Re: Can not able to access https site
Posted: Thu Oct 22, 2020 11:10 am
Client Faced 3 Problems
1) Visiting the Website shows "connection failed <website-name>:443"
This happens unexpected and on very few websites
This has been a problem already discovered in SafeSquid Version [2020.0305] and previous Built
Note: SafeSquid's Builds are Provide With "Year-MonDay-Time" Format, i.e for the above version it states that it is of March 5 2020 release
In order to solve the problem, we need to upgrade the SafeSquid-SWG Binary to latest version [2020.1013]
2) Connect Failed on Websites search functionality
After Properly analyzing the Setup, the website and SafeSquid Configuration we found that the Default SafeSquid System Configuration to Response Header Timeout from Server is "6 SECONDS" and the webserver was not able to respond back in that time frame.
we also analyzed that since it is only faced in Search Functionality which depends upon the web application working and time it takes to fetch data from database and respond back, we need to extend the Timeout Setting specifically for this web application or for these type of Slow Web Applications.
We did so by Changing the Timeout Param to "40 Seconds".
On Direct Internet the Web Application took more than "40 SECONDS" and therefore we then have to increase it to higher number [120 SECONDS]
3) We also show Server Side SSL Chain Misconfiguration on : [https://eaindustry.nic.in/]
SSL Checker Result:
For More Details Visit the Link:https://www.sslshopper.com/ssl-checker. ... ry.nic.in/
1) Visiting the Website shows "connection failed <website-name>:443"
This happens unexpected and on very few websites
This has been a problem already discovered in SafeSquid Version [2020.0305] and previous Built
Note: SafeSquid's Builds are Provide With "Year-MonDay-Time" Format, i.e for the above version it states that it is of March 5 2020 release
In order to solve the problem, we need to upgrade the SafeSquid-SWG Binary to latest version [2020.1013]
2) Connect Failed on Websites search functionality
After Properly analyzing the Setup, the website and SafeSquid Configuration we found that the Default SafeSquid System Configuration to Response Header Timeout from Server is "6 SECONDS" and the webserver was not able to respond back in that time frame.
we also analyzed that since it is only faced in Search Functionality which depends upon the web application working and time it takes to fetch data from database and respond back, we need to extend the Timeout Setting specifically for this web application or for these type of Slow Web Applications.
We did so by Changing the Timeout Param to "40 Seconds".
On Direct Internet the Web Application took more than "40 SECONDS" and therefore we then have to increase it to higher number [120 SECONDS]
3) We also show Server Side SSL Chain Misconfiguration on : [https://eaindustry.nic.in/]
SSL Checker Result:
- sslerror_on_eaindustry_nic_in_website.png (155.2 KiB) Viewed 1830 times
For More Details Visit the Link:https://www.sslshopper.com/ssl-checker. ... ry.nic.in/