Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Aug 26, 2009 04:19 PM|LINK
Not sure if this will help but in my case I figured it out.
The fix was to include the FULL path when linking to an https resource
I was leaving off the the last slash. Not sure if it was the client or the server messing it up. But that fixed it.
It was wierd for sure.