CODEWITHSUNDEEP
debuggingssl
Craig Hyatt
Craig Hyatt

Reputation: 1191

What's the best strategy to diagnose/determine what is causing mixed-content warnings in your web application?

Is there some sort of profiling tool available? View source and search/replace?

Upvotes: 2

Views: 443

Answers (3)

JB King
JB King

Reputation: 11910

WireShark may also be of some help if you want something besides Fiddler, Firebug or HttpWatch for tools to try to resolve the issue.

Upvotes: 0

JoshBerke
JoshBerke

Reputation: 67068

I used view source which helps, although you might want to get a tool that lets you see the current source of the page like firebug in firefox.

One thing I ran into where this didn't help is if you have an iFrame in IE6 without a src attribute. IE6 will warn you about mixed content. No ammount of viewing source helped with this.

Edit

Not sure why I didn't suggest this but you try using Fiddler? Or another packet sniffer? This should let you see ssl traffic, which might help you narrow it down.

Upvotes: 1

Ned Batchelder
Ned Batchelder

Reputation: 375574

Although the message is usually a problem in IE, loading the page in Firefox with Firebug will let you see what is going on.

Also, you might find it helpful to leave the protocol off of the URLs in the first place: Http-https transitions and relative URLs.

Upvotes: 2

Related Questions