Opened 5 years ago
Closed 5 years ago
#18237 closed defect (fixed)
Legacy XHR allows Content-Type header to be set twice
| Reported by: | Colin Snover | Owned by: | Colin Snover |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.4.6 |
| Component: | IO | Version: | 1.7.5 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Bad logic causes someone setting contentType argument *and* a content-type header to set the header twice. (This is not an issue with new dojo/request code.)
Change History (1)
comment:1 Changed 5 years ago by
| Milestone: | 1.7.6 → 1.4.6 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
1.7: 33e102d 1.6: 31ff515 1.5: 4695f6a 1.4: 3036b23