User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20091221 Firefox/3.5.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/20091221 Firefox/3.6 Our Java application sets cookies (actually Tomcat sets them, we do a request.getSession()) in the form of JSESSIONID. However when using Firefox 3.6 with JRE 1.6.0_13 the cookie is not set. We get a 401 status code in response from the servlet. To address this we tried the following without any avail. a. accepting third party cookies b. clearing all cookies c. clearing cache d. editing "about:config" cookie settings. Here are some more observations: Cookie is set properly for following: 1. Firefox 3.5.7 and JRE 1.6.0_13 combination. 2. Firefox 3.6 and JRE 1.6.0_14 combination 3. Firefox 3.6 and JRE 1.6.0_18 combination. Please advise. Reproducible: Always Steps to Reproduce: 1.Set a session on a Servlet and return session id in response. Actual Results: The cookie in the form of JSESSIONID is not set in the FF 3.6 Expected Results: The cookie in the form of JSESSIONID should be set in FF3.6 for JRE 1.6.0_13
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles Also, ensure you update all your plugins (Flash, Reader, java, quicktime, etc) to the latest version available on the vendor's website.
Whiteboard: [CLOSEME 2011-2-25]
No reply, INCOMPLETE. Please retest with Firefox 4 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
The issue is not seen with latest versions of JRE and Firefox. Please mark the bug appropriately and close it. Thanks for the support.
You need to log in before you can comment on or make changes to this bug.