This morning at work we had a conundrum – one of our client’s websites was displaying the infamous “This page contains unsecured content” message when you navigate to the secured (HTTPS) version of their website.
In order to work out which parts of the page were making references to unsecured (HTTP) content, I could either start by trial and error and target code I believe might be causing the problem. Possibly time-consuming and in the end no guarantee I will work it out.
Enter Google Chrome. This new little beauty has a built in debugging console, which allows me to inspect JS elements on the page, or view any errors which are thrown. and coincidentally, it perfectly listed all the URLs which were being referenced via the unsecured scheme. It’s unreal. Just saved me 10-20 mins of unnecessary work.
Related posts:
- Google Chrome: My thoughts Well first thing i have to state is that unlike...
- Google Chrome is Live! http://www.google.com/chrome Downloading and installing it now… In a way, i’m...
- FireFox hit back at Chrome In a stunning display of dick-measuring, FireFox has countered Google’s...
- Chrome App Extensions In the last few weeks I happened to come across...
- Scripting Google Chrome for OSX using AppleScript When it comes to software tools, i like to spend...
