search

ezpaarse-project / ezpaarse

ezPAARSE can ingest your (proxy) log files and show how users access suscribed electronic ressources.
http://www.ezpaarse.org
Other
70 stars 27 forks source link

Error not immediatly fired on client-side #10

Closed nojhamster closed 8 years ago

nojhamster commented 9 years ago

When the format of the first line can't be recognized, the server ends the response but the client doesn't do anything, and the progress bar freezes at its current progress.

The other errors are correctly handled on client side, probably because the response is immediate in those cases. In case of unknown format, the request has to be read a bit before the error can be sent.

nojhamster commented 9 years ago

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

nojhamster commented 8 years ago

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 commented 8 years ago

Bien joué ! Le 3 mars 2016 6:54 PM, "Yannick Schurter" notifications@github.com 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 https://github.com/ezpaarse-project/ezpaarse/issues/10#issuecomment-191886327 .