Issue 843: Invalid Content-Type in GET request to follow a 302 redirect from a POST request http://code.google.com/p/chromium/issues/detail?id=843
Comment #15 by [EMAIL PROTECTED]: Yes, the JIRA fix is just a workaround, to tolerate a Content-Type header in a GET request. The real issue is in the browsers (Safari and Chromium). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
