Opened 10 years ago
Closed 9 years ago
#12141 closed defect (fixed)
Provide a way to not include Content-Type header on an XHR
| Reported by: | rmurphey | Owned by: | Kenneth G. Franqueiro |
|---|---|---|---|
| Priority: | high | Milestone: | 1.7 |
| Component: | General | Version: | 1.5 |
| Keywords: | Cc: | rmurphey | |
| Blocked By: | Blocking: |
Description
There is currently no way to not send a Content-Type header with an XHR; it is set to "application/x-www-form-urlencoded" if one is not specified in the ioArgs.
This became a problem for me because the s3 hash our application uses does not expect the Content-Type header to be there by default. While I can see the benefit of specifying something by default, as of 1.5 there is no way to choose whether the header is present at all.
Attachments (2)
Change History (7)
comment:1 Changed 10 years ago by
| Cc: | rmurphey added; [email protected]… removed |
|---|---|
| Milestone: | tbd → 1.6 |
| Owner: | changed from anonymous to dante |
Changed 10 years ago by
| Attachment: | xhr-content-type.diff added |
|---|
Allow specifying no Content-Type on XHR
comment:3 Changed 10 years ago by
| Milestone: | 1.6 → 1.7 |
|---|
Changed 9 years ago by
| Attachment: | xhr25325.diff added |
|---|
Same changes as original diff, applied as of r25325.
comment:5 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
+1, might not be able to sneak into 1.6 though, bit late. I'll set the milestone to 1.6 and see if anyone notices/complains.