Anonymous User
June 07, 2013 12:23AM
Maxim,

I dug a bit deeper and here is the nginx access log showing the 499 status request, and then a repost of the same request:

XX.XX.XXX.253 - - [06/Jun/2013:21:09:08 -0700] "POST /actions/execute.php HTTP/1.1" 499 0 "https://dev.mydomain.com/execute" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36"

XX.XXX.XXX.253 - - [06/Jun/2013:21:11:32 -0700] "POST /actions/execute.php HTTP/1.1" 200 673 "https://dev.mydomain.com/execute" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36"

I obviously need a solution, since I am essentially creating duplicate transactions. This only happens when the execute.php takes a long time though. In jQuery when I am making the AJAX request I am setting the timeout to 15 minutes. Is there anything else I can look at or try?

Thanks for the help.
Subject Author Posted

HTTP status code 499 from long running requests

Anonymous User June 01, 2013 09:09PM

Re: HTTP status code 499 from long running requests

Maxim Dounin June 02, 2013 07:06AM

Re: HTTP status code 499 from long running requests

Anonymous User June 04, 2013 12:52AM

Re: HTTP status code 499 from long running requests

Maxim Dounin June 04, 2013 07:30AM

Re: HTTP status code 499 from long running requests

Anonymous User June 07, 2013 12:23AM

Re: HTTP status code 499 from long running requests

Maxim Dounin June 07, 2013 10:44AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 292
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready