Jump to content

Edit History

TigranHak

TigranHak

On 12/7/2020 at 3:38 PM, mohamedvasif said:

Hi, 

i face the same issue. and we have narrowed it down. the issue comes only from chrome browser and the module developer has given the below solution

"Please find below soltuion for Chrome null session response issue: The issue where cookies are getting NULL in return journey is occurring with chrome browser 84+ version. There is no restriction from PayU's end as such for cookies .

Solution Suggested:The chrome 84 security update says that SameSite attribute of cookie will be Lax(allowed for GET requests) by default and if we want cookie to travel then it should be marked SameSite : None and "Secure" explicitly. (Ref. https://web.dev/samesite-cookies-explained/"

 

 

Can anyone tell me how to apply this fix.

 

Thanks

We have the exact same problem and we have been informed from one of our partners, that it is due to Chrome Security Update on version > 84

Has anybody managed to solve this?

 

 

Update: I managed to solve this following some suggestions in this topic: 

specifically the part of code that you need to put in the .htaccess file 

Presta 1.7.3.3 here.

TigranHak

TigranHak

On 12/7/2020 at 3:38 PM, mohamedvasif said:

Hi, 

i face the same issue. and we have narrowed it down. the issue comes only from chrome browser and the module developer has given the below solution

"Please find below soltuion for Chrome null session response issue: The issue where cookies are getting NULL in return journey is occurring with chrome browser 84+ version. There is no restriction from PayU's end as such for cookies .

Solution Suggested:The chrome 84 security update says that SameSite attribute of cookie will be Lax(allowed for GET requests) by default and if we want cookie to travel then it should be marked SameSite : None and "Secure" explicitly. (Ref. https://web.dev/samesite-cookies-explained/"

 

 

Can anyone tell me how to apply this fix.

 

Thanks

We have the exact same problem and we have been informed from one of our partners, that it is due to Chrome Security Update on version > 84

Has anybody managed to solve this?

 

Update: I managed to solve this following some suggestions in this topic:

specifically the part of code that you need to put in the .htaccess file 

Presta 1.7.3.3 here.

×
×
  • Create New...