Bug Tracker

Changes between Initial Version and Version 1 of Ticket #5428


Ignore:
Timestamp:
Oct 30, 2009, 8:30:40 PM (10 years ago)
Author:
dmethvin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5428

    • Property Keywords ie content-type added
    • Property Component changed from unfilled to ajax
  • Ticket #5428 – Description

    initial v1  
    99content-type: application/x-www-form-urlencoded
    1010
    11 There are already some reports about encoding problems when using ajax, specially in Internet Explorer. Tickets 3611 (and the duplicates 4315 and 4408) are related to this, however they are about the serialization of the data, not about the headers. Ticket 4855 may be related too, but is a different issue.
     11There are already some reports about encoding problems when using ajax, specially in Internet Explorer. Tickets #3611 (and the duplicates #4315 and #4408) are related to this, however they are about the serialization of the data, not about the headers. Ticket #4855 may be related too, but is a different issue.
    1212
    1313So, I think that we should have, at least by default, to add the missing "; charset=UTF-8" in the content-type header of the IE's XMLHttpRequest. This would reduce encoding problems encountered by developers and users giving the possibility of more and better solutions and workarounds for the remanescent ones. This plays better with jQuery compatibility between different browsers too.