When sending the user to a checkout page, they are switched from http://sitename.com
to https://sitename.com
.
As a result, $_SESSION
variables are lost.
The site has a valid SSL certificate which may or may not be of some use.
When sending the user to a checkout page, they are switched from http://sitename.com
to https://sitename.com
.
As a result, $_SESSION
variables are lost.
The site has a valid SSL certificate which may or may not be of some use.
I have got a solution by this..Try it.
Don't worry this is a normal behavior because HTTPS is meant to be secure and it is doing his part.
Below are some tricks through which you can maintain the session while switching from HTTP to HTTPS.
Transmit session ID between page using GET
POST session ID by POST
Use files to save sessions
Use Cookies for sessions
Use database to save session
Hope you will get something through my reply.
You can manage session between HTTP to HTTPS or HTTPS to HTTP:
Transmit session ID between page using GET
POST session ID by POST
Use files to save sessions
Use Cookies for sessions
Use database to save session
Below example can be used to transmit using GET….
File : http.php ……………
File: https.php ……………
IE7 : This page contains both secure and nonsecure items
You have to use relative path for all static resource on page like css, js, images, flash etc. to avoid IE message secure and nonsecure items…
IE Message
Looks like your session cookie is created with the secure flag, but there's something with the url of your checkout page due to which the session cookie isnt being passed over.
Or probably, your session cookie isnt secure - just that the url of the checkout page is different enough (http://mysite.com vs http://www.mysite.com) that the browser isnt sending the cookie.
If you'd like to read more on flipping over from http to https and vice versa - do take a look at at my writeup on selective ssl :-)
This may not be possible since the cookie seems to be getting lost. The browser you're using must think it's for a completely different domain.
What browser are you using specifically?
Think about using HTTPS for all pages, that's the easiest way to avoid this problem and it will improve the security of your site.
If SSL for all pages is not an option to you, then you could use this approach: Switching between HTTP and HTTPS pages with secure session-cookie. The idea behind is, that you leave the session cookie unsecure (and therefore available to HTTP and HTTPS pages), but have a second secure cookie to handle the authentication. It's a good way to separate the two concerns "maintaining the session" and "authentication".