Q: How to find out not secure connected page when security connection is already implemented on site?
A: Page security is a needed verification step by QA/QA Team after implementation on site but sometimes one or more of those pages may not be connected and there security can be break. So a QA/QA Team should not forget to work on that.
Many automation techniques are available to find out not secure connected page. Process can be done by manually also but this will take enough time and one or more pages may be there those are not found by tester/team.
There is one simple technique also available to get insecure page by module to module. Just need to open the module of site what needed to be verified then run the command “Ctrl+U” now code will be visible there and now need to run “Ctrl+F” then find insecure page if page is there then will be highlighted there.
Command can be changed according to “OS” but process will be same for finding not secure connected page if getting any reason about commands not working then in simply way use the “right click then select source code of page and further find unsecured page which is not connected with HTTPS”
Finding not secure connected page related case can also be used by using any link related testing tool so first thing will be needed to run tool then all pages link will be fetched there after completing of executing then use find command and use keyword like “http” then pages will be highlighted and find site’s pages if any page is there then definitely it will be a simple trick to this case about not secure connected page.
Example with founded links:- Suppose previously pages was called from “http://……com” then after implemented “SSL” pages must be called from “https://test.com”. There should not be called any page, image or any source from “http”.