Correct, this was a work around for a pre-1.5 FF issue. My notes on it say "see mozilla bug #246651" but I remember thinking that jQuery was using the same work around as another js library (prototype?) and that that project had its own bug to get rid of the work around. I thought I saw that the work around had finally been removed in more recent versions of jQuery. I last patched a 1.0.4 version for local use at work but I think it was there until 1.1.
There was also another reason for explicitly closing the connection that Jake Cigar(?) asked for when overriding the mime type of the request. I forget his reasons for that right now. Ian On 4/10/07, Aaron Heimlich <[EMAIL PROTECTED]> wrote:
I vaguely remember there being some issue with older versions of Firefox that this solved, but don't quote me on that. On 4/10/07, Priest, James (NIH/NIEHS) [C] <[EMAIL PROTECTED]> wrote: > > I've been implementing Dan Switzer's autocomplete plugin on my site and > I have everything sort of working (thanks Dan!) but ran into an issue > with authentication. My site uses Windows Integrated Authentication (on > IIS) and every Ajax request kicks off a login prompt... > > Dan found this: > http://anotherdan.com/2006/6/8/ajax-and-integrated-windows-authenticatio > n > > I replaced my compressed jQuery script with the source and commented out > that line: > > // transport.setRequestHeader("connection", "close"); > > Which seems to have solved this issue. But I want to make sure this > doesn't screw up anything else?? > > Also - how can I re-compress my source with this modification included? > > Thanks, > Jim > -- Aaron Heimlich Web Developer [EMAIL PROTECTED] http://aheimlich.freepgs.com