No, I don't set the cache property. But I use the 'script' data type for the query (because I want to avoid cross-domain issues) and the jQuery code explicitly sets cache to false when using 'script'.
It seems as if I should explicitly set cache to true in my case. But that's really a workaround, and is not semantically correct -- I don't want caching, but I don't want the hidden URL parameter either. I would think there should be a way to satisfy this use case. Thanks and regards. On Oct 21, 10:00 pm, "Erik Beeson" <[EMAIL PROTECTED]> wrote: > That parameter is added when you set the 'cache' property to false. Are you > doing that? > > --Erik > > On 10/21/07, M. A. Sridhar <[EMAIL PROTECTED]> wrote: > > > > > When making a GET call via jQuery.ajax, jQuery 1.2.1 adds a URL > > parameter named '_' (the single underscore character) whose value is > > the current time stamp. I'm not sure I understand why, and in any > > case, this caused me some grief when I tried to use it in a Facebook > > app. The reason is that the Facebook API requires a "signature" > > parameter as part of each request, and this parameter is basically the > > MD5 hash of the rest of the parameters. So the extraneous jQuery > > parameter was not being accounted for in my code, causing Facebook to > > complain about an incorrect signature. > > > Perhaps someone can explain the need for this parameter. And perhaps > > it can be made optional in a future release? > > > Just my $0.02. > > > Regards.
