nEMESIS4
10-04-2001, 01:43 PM
Has anybody else had this problem. Occasionally when a user on on of our ecommerce sites proceeds to the order form page it times out instantly. Then when you refresh the page comes back up. This is the point where it switches to the secure certificate.
This is an explenation from a tech support person from the company that designed our ecommerce package... Does anybody know how to fix this problem?
------
We believe this is due to the handoff from the https on systems that are running Apache 1.3.# {Red Hat Secure/2.0 (Unix) mod_ssl/2.0.15 SSLeay/0.9.0b on Linux}.
Your RAQ appears to be running: Apache/1.3.20 Sun Cobalt (Unix) mod_ssl/2.8.4 OpenSSL/0.9.6b PHP/4.0.4pl1 mod_auth_pam_external/0.1 FrontPage/4.0.4.3 mod_perl/1.25 on Linux
In our experience, the problem you describe happens in the secure mode and is an instant 404 rather than a 404 after several seconds. This implies that it is not a time-out issue, but rather that the server can't respond at that millesecond to valid URL request. Specifically, any IP based host running their own cert are most likely to have the problem. The problem is less likely to occur in a 'shared' certificate environment.
This is an explenation from a tech support person from the company that designed our ecommerce package... Does anybody know how to fix this problem?
------
We believe this is due to the handoff from the https on systems that are running Apache 1.3.# {Red Hat Secure/2.0 (Unix) mod_ssl/2.0.15 SSLeay/0.9.0b on Linux}.
Your RAQ appears to be running: Apache/1.3.20 Sun Cobalt (Unix) mod_ssl/2.8.4 OpenSSL/0.9.6b PHP/4.0.4pl1 mod_auth_pam_external/0.1 FrontPage/4.0.4.3 mod_perl/1.25 on Linux
In our experience, the problem you describe happens in the secure mode and is an instant 404 rather than a 404 after several seconds. This implies that it is not a time-out issue, but rather that the server can't respond at that millesecond to valid URL request. Specifically, any IP based host running their own cert are most likely to have the problem. The problem is less likely to occur in a 'shared' certificate environment.
