You searched for the word(s):
< 1 second(s)
Thanks, but we've gone through the config files looking for anything that may point to an outside site, anything starting with HTTP, and as far as we can tell it's all been stripped out. I've gone through the asp page that the cute control sits on but all of those links are relative and are happily within the HTTPS ...
We have the same problem, using version 6 of the .NET cutesoft control, and have gone through the above steps.
We still get a secure/non secure message appear on our HTTPS site.
Any resolution for this in 6?