We have a couple of fields on a web page, one is for logging into our system
the other is just a plain zip code store locator. When in https (SSL) mode,
we are getting complaints from people that they are unable to login. I
spoke to one person directly and the login and password were correct. So I
had him try the zip code store finder and that did not get past the default
page for either of the submission types. His browser build version and
security settings were identical to mine.
I had him trust our website URL in his browser and then he was able to login
and search for a store. So my question is, is there something not apparent
wrong with our certificate, or could this be a coding issue? My operations
manager swears that the certificate is correctly installed.
This is something that I have not been able to replicate on any of the
systems in the office or our homes.
Any ideas?
Velvet
the other is just a plain zip code store locator. When in https (SSL) mode,
we are getting complaints from people that they are unable to login. I
spoke to one person directly and the login and password were correct. So I
had him try the zip code store finder and that did not get past the default
page for either of the submission types. His browser build version and
security settings were identical to mine.
I had him trust our website URL in his browser and then he was able to login
and search for a store. So my question is, is there something not apparent
wrong with our certificate, or could this be a coding issue? My operations
manager swears that the certificate is correctly installed.
This is something that I have not been able to replicate on any of the
systems in the office or our homes.
Any ideas?
Velvet
Comment