1274010 - xmlhttprequest post randomly failing

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[Greg]

Attachment: Showing non action of post request

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160502172042

Steps to reproduce:

This is not reproducible at will.  Very randomly an xmlhttprequest will just die.  No error message, no results, nothing. This has started lately an affects a lot of our app users.


Actual results:

Non completion of the xmlhttprequest.


Expected results:

A successful http 200 return code, plus a payload.

Comment 1

[Loic]

It's surely a dupe of bug 1269055 which is fixed in 47+. You can install Beta and test yourself: https://www.mozilla.org/en-US/firefox/beta/all/

Reopen the bug if that's not the case.

Comment 2

[Liz Henry (:lizzard) (relman/hg->git project)]

Greg, here's a suggestion from our developers for a workaround:  Adjust your server side persistent connection timeout to be about 5 seconds longer than the firefox value. Firefox uses 115 seconds for HTTP/1.x and 180 seconds for HTTP/2.  

Hope that helps. If you try it, please let us know the result.

Comment 3

[Greg]

I'll mention this to tech support, but our server is one of hundreds at a server farm.  But we'll see what they say.  Thank you.

Comment 4

[Greg]

In reading some of the comments on bug 1269055 I'm not certain this is a duplicate, but it's definitely related.  In our case the (async ajax) POST didn't succeed or fail, it just did nothing. And there was no error in the server side logs. You can see that from the screen shot I included.  We catch success or fails, but nothing was caught, it's as if the POST never happened.  Also, the POST in the screen shot should have taken no longer than a second to complete. So the server taking longer than 115 seconds would be very odd.  Looking back at the FF46 release dates, 46.0.1 would roughly coincide from when we started getting reports of random failures.

Comment 5

[Loic]

Greg, can you test with Beta 47 and confirm it's fixed on your side with your app.
https://www.mozilla.org/en-US/firefox/beta/all/

Comment 6

[Greg]

I can certainly download the beta.  But there is no way to know for certain if it's fixed as getting the error to show up is random.  However, if it went 3-4 days without an error it would probably mean it's fixed.

Comment 7

[Justin [:JW_SoftvisionQA]]

Hey Greg, has this issue came up again in the past 3 days?

Comment 8

[Justin [:JW_SoftvisionQA]]

closing this issue due to lack of response from the reporter. Please reopen if this issue persists.