On Fri, Apr 4, 2008 at 11:48 PM, John-David Dalton
[EMAIL PROTECTED] wrote:
This ticket here: http://dev.rubyonrails.org/ticket/11434 mentions
asolution for dropped connections in Firefox. It might work on other
browsers as well. Basically they attach a callback to the onError
native
[correction]
Should it just be?
return (status = 200 status 300);
- Jon L.
On Apr 4, 4:50 pm, Jon L. [EMAIL PROTECTED] wrote:
(ref:http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thr...)
On Apr 4, 4:38 am, Ree [EMAIL PROTECTED] wrote:
Hello,
Here's a simple
On Fri, Apr 4, 2008 at 4:01 PM, Jon L. [EMAIL PROTECTED] wrote:
[correction]
Should it just be?
return (status = 200 status 300);
- Jon L.
status is zero for local ajax calls which are used for unit testing
and potentially used for offline development. See my patch, which, as
Also a different patch for solving the same problem.
I check the window.location.href and the url of the ajax call to
determin if its file or ftp protocol then allow zero or not.
http://dev.rubyonrails.org/ticket/10030
--~--~-~--~~~---~--~~
You received this
On Fri, Apr 4, 2008 at 11:01 PM, John-David Dalton
[EMAIL PROTECTED] wrote:
Also a different patch for solving the same problem.
I check the window.location.href and the url of the ajax call to
determin if its file or ftp protocol then allow zero or not.
This ticket here: http://dev.rubyonrails.org/ticket/11434 mentions
asolution for dropped connections in Firefox. It might work on other
browsers as well. Basically they attach a callback to the onError
native event handler of the transport.
--~--~-~--~~~---~--~~
