Recently, my web sites have been sending out two confirmation emails for orders submitted. Both the web site owner and the customer get the duplicate emails. Occasionally, these emails have been sent out in triplicate!
This behavior began conspicuously after updating (GoDaddy.com) security certificates. Recently GoDaddy has required 2048-bit encryption keys. No one I've talked to--including GoDaddy techs think that the certificates have anything to do with this behavior.
However, further testing revealed that when an order is submitted on one of these sites, the response page (which sends out the emails) will be called at least twice--one under HTTPS and the other under normal HTTP!
I have a function that allows me to force SSL on for pages where it is desireable. Here's the code:
I have a similar routine to turn SSL off for a given page.
You can see that the routine tests the SERVER_PORT_SECURE variable to determine whether SSL is available, and then redirects using HTTPS if it is. It looks to me like the original request is being served despite the redirection.
I'm still confused why these new 2048-bit certs would cause this to happen. I don't believe this happens on sites that haven't got the renewed certificates.
The server is Windows 2003 and IIS6. Any insights would be appreciated.
Thanks in advance,
Ron
This behavior began conspicuously after updating (GoDaddy.com) security certificates. Recently GoDaddy has required 2048-bit encryption keys. No one I've talked to--including GoDaddy techs think that the certificates have anything to do with this behavior.
However, further testing revealed that when an order is submitted on one of these sites, the response page (which sends out the emails) will be called at least twice--one under HTTPS and the other under normal HTTP!
I have a function that allows me to force SSL on for pages where it is desireable. Here's the code:
Code:
'#######
'SSLOn(string cPath) : null
' If the application is currently running on regular HTTP, and
' DISABLE_SSL is FALSE, redirect to HTTPS Call within a page that
' you wish to send over a secure connection, providing the file
' name of the page as an argument. WARNING: May call
' Response.Redirect, ending execution of the ASP page
'#######
Sub SSLOn(cPath)
Dim nSecure, cURL, cServerName
nSecure = Request.ServerVariables("SERVER_PORT_SECURE")
If nSecure <> 1 Then
cURL = "[URL unfurl="true"]https://"[/URL] & Request.ServerVariables("HTTP_HOST") & _
Request.ServerVariables("URL") & "/../" & cPath
' Forget about trying to use SSL on the local host.
cServerName = Request.ServerVariables("SERVER_NAME")
If not DISABLE_SSL Then
Response.Redirect cURL
'Response.Write "Redirect to: " & cURL
else
if not DISABLE_SSL_WARNING then
call Notice("SSL Disabled", _
"User name, password, and any other " &_
"information you enter will not be transmitted " &_
"securely and could potentially be viewed by " &_
"others. SSL should only be disabled when " &_
"necessary during testing, and real accounts " &_
"should not be used while SSL is disabled.")
end if
End If
End If
End Sub
I have a similar routine to turn SSL off for a given page.
You can see that the routine tests the SERVER_PORT_SECURE variable to determine whether SSL is available, and then redirects using HTTPS if it is. It looks to me like the original request is being served despite the redirection.
I'm still confused why these new 2048-bit certs would cause this to happen. I don't believe this happens on sites that haven't got the renewed certificates.
The server is Windows 2003 and IIS6. Any insights would be appreciated.
Thanks in advance,
Ron