Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Web Application breaks because of Total Cookie Protection

  • 1 antwoord
  • 0 hierdie probleem
  • 10 views
  • Laaste antwoord deur cor-el

more options

We have a very old web application which requires JSESSION_ID to be stored in cookies for our login session. As part of our solution, we provide a HTML document in which we embed the URLs of our web application. This HTML document can be opened locally, but, it tries to contact our application for Login validation. As part of that it needs to access the JSESSION_ID.

Before Total Cookie Protection was made default, the application was working fine. But, after making it default, we are observing 2 behaviors which are breaking our application. Those 2 behaviors are: 1. When we click on a button to open the document, nothing happens. We checked the console logs and the network tab in the Browser developer tool, but we couldn't find anything. 2. Sometimes, browser is sending wrong JSESSSION_ID. Here also, we couldn't find anything in browser developer tool.

Once, we disable Total Cookie Protection both the above problems goes away. We checked Firefox's documentation : https://developer.mozilla.org/en-US/docs/Web/API/Storage_Access_API) and we found that our application has un-partitioned storage to cookie jars.

We are looking for pointers on how to fix this problem. Thank you.

We have a very old web application which requires JSESSION_ID to be stored in cookies for our login session. As part of our solution, we provide a HTML document in which we embed the URLs of our web application. This HTML document can be opened locally, but, it tries to contact our application for Login validation. As part of that it needs to access the JSESSION_ID. Before Total Cookie Protection was made default, the application was working fine. But, after making it default, we are observing 2 behaviors which are breaking our application. Those 2 behaviors are: 1. When we click on a button to open the document, nothing happens. We checked the console logs and the network tab in the Browser developer tool, but we couldn't find anything. 2. Sometimes, browser is sending wrong JSESSSION_ID. Here also, we couldn't find anything in browser developer tool. Once, we disable Total Cookie Protection both the above problems goes away. We checked Firefox's documentation : https://developer.mozilla.org/en-US/docs/Web/API/Storage_Access_API) and we found that our application has un-partitioned storage to cookie jars. We are looking for pointers on how to fix this problem. Thank you.

All Replies (1)

more options