Opened 10 years ago
Closed 9 years ago
#5757 closed bug
jQuery 1.3.2 document.ready() event does not fire with persistent proxy connections
| Reported by: | censornet | Owned by: | censornet |
|---|---|---|---|
| Priority: | critical | Milestone: | 1.4 |
| Component: | event | Version: | 1.3.2 |
| Keywords: | ready | Cc: | |
| Blocked by: | Blocking: |
Description
We develop a web proxy server which impliments client side HTTP persistent connections. This seems to cause a bug in jQuery's docuemnt.ready() event handling, resulting in it failing to fire while the persistent connection (socket) to the proxy server from the web browser remains open.
This results in web pages which use the document.ready() event failing to load until the socket times-out and closes.
I have attached a packet capture file (pcap) which can be opened with the free Wireshark network protocol analyser. It shows the browser using a persistent connection to make requests to the proxy server which (as expected) remains open at the end of the transactions. This (I think) is the cause of the problem in jQuery's ready event handling logic.
Attachments (1)
Change History (4)
Changed 10 years ago by
| Attachment: | jquery_problem_http_transactions.zip added |
|---|
comment:1 Changed 10 years ago by
comment:2 Changed 9 years ago by
| Owner: | changed from brandon to censornet |
|---|---|
| Status: | new → pending |
I'm going to set this as pending since there's no live test case we can analyze. Please reopen if you can provide one, otherwise it will be closed as invalid. Thanks!
comment:3 Changed 9 years ago by
| Status: | pending → closed |
|---|
Automatically closed due to 14 days of inactivity.
Do you only see the problem with Firefox 3.5, or is it happening on other browsers as well?
Can you provide code for a test case? It would help in understanding the sequence of events going on there.