Error not immediatly fired on client-side about ezpaarse

[nojhamster]

This problem affects ajax requests in both chrome and firefox, but cURL behaves correctly.

[nojhamster]

The server was sending the headers along with the heartbeat, that's why the status code couldn't be set in case of wrong format. Now it waits for at least one line to be parsed before it initiate the heartbeat.

Edit: I just noticed this issue was not exactly the same, but it seems that it's been fixed as well.

[pseudom]

Bien joué !
Le 3 mars 2016 6:54 PM, "Yannick Schurter" [email protected] a
écrit :

The server was sending the headers along with the heartbeat, that's why
the status code couldn't be set in case of wrong format. Now it waits for
at least one line to be parsed before it initiate the heartbeat.

—
Reply to this email directly or view it on GitHub
#10 (comment)
.