User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/2009021906 Firefox/3.0.7 GTB5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/2009021906 Firefox/3.0.7 GTB5 When the path component of the URI is very long (in my case, 1270 characters) and the POST response would set a cookie (Set-Cookie response header), the cookie is not actually saved by Firefox. If the URI parameters are very long and the URI path is short, then there is no problem. Hasn't been tested with shorter URI to see where the problem starts to show up. Reproducible: Always Steps to Reproduce: 1. POST data to a page with a very long URI path that responds with a Set-Cookie header. 2. Send a GET request to the same domain / URI. Actual Results: The Cookie header will not be present in this request. If the URI path is shorter, Cookie will have been saved. Expected Results: The Cookie should have been saved and sent with the GET request. 1. See attached file 'info.php' used for testing this bug. The path where 'info.php' is stored should be very long, such that the total URI length is >= 1270 characters. It may also happen with shorter URIs; I didn't find the limit. With a much shorter URI (100 characters), there is no problem. 2. No installed Add-ons, using defaul theme.
Created attachment 369754 [details] Test page that shows request details (renders in quircks mode) using PHP
Attachment #369754 - Attachment mime type: text/html → text/plain
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.