Curt_C wrote:
fully path out the error page perhaps, including the HTTPS://
With SSL it's the best way to ensure you dont switch secutity contexts and
cause issues.
By the way... sounds like WebHost4Life? (had similar issue but didnt really
pursue it).
--
Curt Christianson
site: http://www.darkfalz.com
blog: http://blog.darkfalz.com
Curt,
Many thanks for taking the trouble to reply. The problem has now been
resolved by my ISP - simplewebhosting - apparently, as they describe
it:
"Looks like the site had some out of date client side .NET javascript
files installed. I have upgraded these, which has corrected the issue
(for what it is worth, only Internet Explorer had trouble with the
login action button, other browsers worked fine throughout)"
Now everything seems to work fine without me having to change a single
line of code from pre-SSL days - SO FAR!!
Dave Rudlin