#7428 closed enhancement (invalid)
Custom Ajax Headers should not require explicit type (GET|POST)
| Reported by: | Rick Waldron | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | ajax | Version: | |
| Keywords: | needsreview, ajaxrewrite | Cc: | john, dmethvin, addyosmani, ajpiano, slexaxton |
| Blocked by: | Blocking: |
Description
This was a byproduct of: http://bugs.jquery.com/ticket/7424
End developer should be able to set custom ajax/xhr headers whether or not the type property is set in a given request.
Change History (6)
comment:1 Changed 13 years ago by
| Cc: | john dmethvin snover addyosmani ajpiano slexaxton added |
|---|---|
| Component: | unfiled → ajax |
| Keywords: | needsreview added |
| Priority: | undecided → low |
comment:2 Changed 13 years ago by
| Cc: | snover removed |
|---|
comment:3 Changed 13 years ago by
I can't see where $.ajax prevents the call to beforeSend, which is where the reporter in #7424 was trying to set headers. Maybe it fell into the jsonp case? A specific test case would help.
comment:4 Changed 13 years ago by
| Keywords: | ajaxrewrite added |
|---|
comment:5 Changed 13 years ago by
There's no limitation I know of in current code that would prevent setting headers based on the type or even dataType options. Of course, whether or not the headers are actually transmitted will depend on the transport (so you can set them all you want when doing jsonp, they won't get sent for cross-domain requests).
comment:6 Changed 12 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Yeah, I don't think there's an issue here.
Note: See
TracTickets for help on using
tickets.
I'd like to open the floor for discussion on this enhancement