Mike10987 wrote:
> http://traininglog.runnersworld.com/landingpage.aspx
When I visit that web page, there is an error on that page (see the
lower left corner in the status bar). The error says the web page
doesn't have permissions to access the /
js/eluminate.
js script file on
their server or they specified a non-existing path. That's something
they will have to fix on their end.
When I click on the Login link, I am taken to:
https://member.rodale.com/cas/login?...security_check
Notice the change in domain (from runnersworld.com to rodale.com). It
is an HTTPS (secure) page. That was as far as I could go since I don't
have an account there but I did get their login web page. Did you
encounter the error before this point (in trying to show the login page)
or was it after you tried to login?
The error you mention probably means the site (which is probably the
rodale.com login page) has an invalid security certificate. The domain
for their SSL cert doesn't match up with the domain that you are at.
However, I didn't get the warning. Have you yet flushed the web
browser's TIF (both files and cookies)? Make sure to also include
favorite sites (i.e., disable the Preserve Favorites option when
deleting files in the TIF). See
https://support.virtbiz.com/index.ph...articl eid=56.
Also, because this is an SSL connect, the time on the server and client
hosts must be within a couple minutes of each other (I don't recall by
how much they are allowed to be different). The handshaking before the
connection is encrypted will check if one end has been idle too long
which invalidates the hash code sent between them. When making an SSL
connect, the attempt times out. If the time is significantly different
between server and client, the handshaking figures it has been too long
and times out the process. So check your time, timezone, and daylight
savings option. If your time is way off (even just a few minutes, or
more) then start using the Windows Time service; however, the default
has every Windows user pointing at the same NTP server which can get
very busy and you might not sync for a long time, so specify a different
NTP server (I haven't done this in a long time and recall you had to add
a registry entry to add other NTP hosts to the list from which you can
select). Or get a 3rd party time sync utility (I use Socketwatch but it
isn't free; Google or search download sites, like download.com or
softpedia.com, on "atomic clock" and "time sync").