Does the jQuery $.ajaxSetup method not respect the data field in the options hash when $.post or $.get is called?

For example, I might have this code:

$.ajaxSetup({ data: { persist: true } });

Then, to send a POST request, I would call this:

$.post("/create/something", { name: "foo" });

I was expecting the actual POST data to look like this:

{
  persist: true,
  name: "foo"
}

but the only data sent by $.post is { name: "foo" }. Is there any way to get the expected behavior? I'm using jQuery 1.4.1.

Does the jQuery $.ajaxSetup method not respect the data field in the options hash when $.post or $.get is called?

For example, I might have this code:

$.ajaxSetup({ data: { persist: true } });

Then, to send a POST request, I would call this:

$.post("/create/something", { name: "foo" });

I was expecting the actual POST data to look like this:

{
  persist: true,
  name: "foo"
}

but the only data sent by $.post is { name: "foo" }. Is there any way to get the expected behavior? I'm using jQuery 1.4.1.

• javascript
• jquery
• ajax

Share Improve this question Follow edited Jun 26, 2015 at 17:26 Sumurai8 20.8k1111 gold badges6969 silver badges102102 bronze badges asked Mar 30, 2010 at 4:55 Justin PolieyJustin Poliey 16.3k77 gold badges3939 silver badges4848 bronze badges

Add a ment  | 

2 Answers 2

Sorted by: Reset to default 6

$.ajaxSetup() sets defaults for your ajax requests. Any options you set in the request method will override these defaults, not merge them. You're actually overriding

{ persist: true }

with

{ name: "foo" }

---

This no longer appears to be the case — a ticket on the jQuery tracker suggests that this was added in a version update and jQuery now merges the objects instead of replacing the default (thanks @Quincy).

As documentation says data option is converted to query string and appended to the URL for GET requests.