I think its going to be difficult for anyone to give you specific help. Without knowing the exact details of yours and the payment system involved.
I think being on HTTPS can affect the way sessions are handled. One issue I know of is that, dependant on settings, a cookie set by HTTPS, must only be read over HTTPS. So maybe if you are moving between https/ http when the user is logged in, this can cause an issue. Also, from my experience, a callback from a payment provider will be treated entirely seperatly from the user of the website (obviously, as it is a differnt computer calling the page entirely). So any controller/actions that the callback calls directly, can not require a user to be logged in. If you need specific data to be remember between the site, the payment page and then the callback, it needs to be passed along in the POST/GET data. I have a payment provider integrated fine into my cakePHP app. I keep everything over HTTPS after the user is logged in, my callback is a cake controller/action that dosn't require login, and the last page servered as part of the payment provider pages redirects the user back to the site, and they remain logged in. On Jun 22, 12:31 pm, Ritesh R Aryal <[email protected]> wrote: > Still looking for your valued response. > Lets brainstorm to have right solution. > > Is this a Session issues ? > > but it is working fine when the site is worked onhttp://sitename.com. > But it gives problem when i get response back from payment page. > > cheers -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
