firefox request aborted

https://github.com/defunkt/jquery-pjax/issues/46

slampis opened this issue 2 years ago

requests aborted

No milestone

No one is assigned

I am often getting requests aborted in Firefox and Google Chrome.
I tried to debug this and found this piece of code

    if ( xhr && xhr.readyState < 4) {
        xhr.onreadystatechange = $.noop
        xhr.abort()
    }

which makes perfectly sense but the requested aborted problem occurs also if there isn't another request pending.
I verified this with this code

    if ( xhr && xhr.readyState < 4) {
        alert('already pjaxing...');
    }

The popup isn't shown but the request often gets aborted. Server side everything works fine.
Any idea about this behaviour?

9 participants

slampis commented 2 years ago

I guess I figured it out. It was caused by the default timeout in the PJAX requests which was to short for me.

tommoor commented 2 years ago

Glad you figured this one out... been banging my head against it all morning trying to figure out whysometimes pjax was working and not others.

This is a particular issue for me with rails in development mode as the timeout is often exceeded.

defunkt commented 2 years ago

You can now change the timeout globally:

$.pjax.defaults.timeout = 5000

Closed

defunkt closed the issue 2 years ago

airstrike commented 2 years ago

Thank you for this! I was experiencing the same problem. Perhaps a bigger default value is in order?

Cheers,
AT

rdewell commented a year ago

I'm also seeing many aborted calls. My app responds in < 1 second, but just to try I increased the timeout to 30000. No luck.

Often I'll see 3 aborted calls to the URL, and then a final successful call to the URL.

Any other things to look into?

dsabanin commented a year ago

I'm seeing the same thing as rdewell. Even if pjax request is under timeout, I see that JS triggers many unnecessary requests to the same URL and only one of them is finished - others are aborted before they proceed. See the screenshot below:

karlentwistle commented 11 months ago

Thanks, I was having this issue as well, using defaults.timeout = 5000 worked.

josh referenced this issue 8 months ago

Closed

Issue #194: Works only half of the time

kromem commented 3 months ago

Just for posterity's sake -- I had been running into this problem, and was tearing my hair out.

I finally realized that I was calling the $.fn.pjax() function in my returned pjax templates with the intention of binding to newly loaded elements.

Apparently that was unnecessary, and I was instead generating multiple requests bound to the handler, and those requests returnedxhr.readyState = 1, leading to aborted requests.

This was compounded when I prevented the timeout, as the number of canceled requests continued to linearly grow and a new page load was never generated.

So for anyone that stumbles across this in the future, and extending the timeout still results in aborted requests (such as@rdewell and @dsabanin above), make sure you aren't binding extra events to your handlers.

(Note: It might be useful if the docs indicated the $.fn.pjax() binds to returned content, and calling again is unnecessary.)

rjquery commented 3 months ago

Perfect. Thank you for the help, this solved my problem.