Cookie generated by ASP.NET form authentication is not saved
I have ASP.NET web site that generate ASP.NET form authentication cookie with machine key. This cookie should be passed to next application. Unfortunately, it is not because is not saved. This work fine until I installed the latest version of Firefox (29). What changed that ASP.NET form authentication cookie is no longer saved in Firefox?
Regards
כל התגובות (6)
Is there a page online demonstrating this problem? If so, it would be great to get a link and a description of the steps to reproduce the problem.
There are hundreds of changes in every release, but many of the highlights can be found in these articles:
- https://developer.mozilla.org/Firefox/Releases/29/Site_Compatibility
- https://developer.mozilla.org/Firefox/Releases/29
Have you tested in a clean profile, in case this problem might be due to a setting, extension, or cookie file corruption in your main profile?
Create a new Firefox profile
A new profile will have your system-installed plugins (e.g., Flash) and extensions (e.g., security suite toolbars), but no themes, other extensions, or other customizations. It also should have completely fresh settings databases and a fresh cache folder.
Exit Firefox and start up in the Profile Manager using Start > search box (or Run):
firefox.exe -P
Any time you want to switch profiles, exit Firefox and return to this dialog.
Click the Create Profile button and choose a name like TEST. Please skip the option to choose a different folder location for the profile. Then start Firefox in the new profile you created.
Check the Add-ons page to make sure all extensions are disabled. Either:
- Ctrl+Shift+a
- orange Firefox button (or Tools menu) > Add-ons
In the left column, click Extensions.
Now, if you test your site, any difference?
When returning to the Profile Manager, you might be tempted to use the Delete Profile button on TEST. But... it's a bit too easy to accidentally delete your "real" profile, so I recommend resisting the temptation. If you do want to clean up later, I suggest making a backup of all your profiles first in case something were to go wrong.
Hi, Thanks for your response. I’ve tested my application (LightSwich VS2013) with new profile. The same issue.
Also, I create a new stay alone LightSwitch HTML project to test my problem. I found that Firefox, ver 30, works fine if domain is full, slstesth1.azurewebsites.net. Before, I have “azurewebsites.net” as domain and it worked fine. It looks like something change with version 29. Microsoft’s technician told me that this is probably issue with cross domain cookies.
Any suggestion???
I don't know whether there were any changes related to "third party" cookies recently.
These articles list some of the major changes in Firefox 29 and 30 from the developer perspective, but since there are thousands of changes in each version, it also could be something subtle or unintended.
Could the issue be a cross-domain post (XMLHttpRequest or iframe)? Firefox's browser console (Ctrl+Shift+j or Developer menu) will log security-related errors such as requests blocked or declined due to cross-domain issues.
For cookies, however, since the result of not sending them usually is to change the response from the server, this may not appear abnormal in the browser console.
Hi J.., Do you know if it is possible to contact Firefox people directly?
At this point, I only know that something changed.
Thanks
Bugzilla is the right place to report the issue. I'm looking for a similar case.
You could send feedback from the Help menu - Submit Feedback. Whether they do anything is another question.