malsup wrote:
>
>> That would be a nice addition. Has there been any discussion of having
>> jQuery automatically use:
>>
>> X-Requested-With: XMLHttpRequest
>
>
> It already does.
>
Excellent! One more reason to keep using it.
--
View this message in context:
http://www.nabble.com/Set
> That would be a nice addition. Has there been any discussion of having
> jQuery automatically use:
>
> X-Requested-With: XMLHttpRequest
It already does.
___
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
Mitchell Lane wrote:
>
> This would allow the programmer to set and override their own HTTP
> headers.
>
That would be a nice addition. Has there been any discussion of having
jQuery automatically use:
X-Requested-With: XMLHttpRequest
...in the headers of its AJAX calls? There's a few differ
I've pinpointed both my issues, and would like to propose the following
changes:
In jquery/jquery.js, line 356, replace:
$.g = {
'': "m[2] == '*' || a.nodeName.toUpperCase() == m[2].toUpperCase()",
with:
$.g = {
'': "m[2] == '*' || a.localName.toUpperCase() == m[2].toUpperCase()",
This would allo
Hi there! I've been impressed with all the work and effort that's gone
into jQuery, and I've decided to try to use it for a WebDAV AJAX
application I'm working on.
I've run into two issues off the bat: the first is that an $.xml (or
$.ajax) call does not seem to support setting your own HTTP he