Skip to main content

Bug Tracker

Side navigation

#7428 closed enhancement (invalid)

Opened November 07, 2010 03:13PM UTC

Closed April 16, 2011 08:52PM UTC

Last modified March 13, 2012 07:11PM UTC

Custom Ajax Headers should not require explicit type (GET|POST)

Reported by: rwaldron Owned by:
Priority: low Milestone:
Component: ajax Version:
Keywords: needsreview,ajaxrewrite Cc: john, dmethvin, addyosmani, ajpiano, slexaxton
Blocked by: Blocking:

This was a byproduct of:

End developer should be able to set custom ajax/xhr headers whether or not the type property is set in a given request.

Attachments (0)
Change History (6)

Changed November 07, 2010 03:15PM UTC by rwaldron comment:1

cc: → john, dmethvin, snover, addyosmani, ajpiano, slexaxton
component: unfiledajax
keywords: → needsreview
priority: undecidedlow

I'd like to open the floor for discussion on this enhancement

Changed November 08, 2010 05:28PM UTC by snover comment:2

cc: john, dmethvin, snover, addyosmani, ajpiano, slexaxtonjohn, dmethvin, addyosmani, ajpiano, slexaxton

Changed November 12, 2010 01:40AM UTC by dmethvin comment:3

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.

Changed December 27, 2010 10:37PM UTC by rwaldron comment:4

keywords: needsreviewneedsreview,ajaxrewrite

Changed January 09, 2011 05:34AM UTC by jaubourg comment:5

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).

Changed April 16, 2011 08:52PM UTC by john comment:6

resolution: → invalid
status: newclosed

Yeah, I don't think there's an issue here.