connect.timeout sends a 408 #719

Closed
ajostergaard opened this Issue Jan 3, 2013 · 3 comments

2 participants

@ajostergaard

A 408 is supposed to be for when "the client did not produce a request within the time that the server was prepared to wait." and more generally 4xx errors are client errors not server errors. Unless I've misunderstood what's being timed a 5xx error is more appropriate.

@tj
Sencha Labs member
tj commented Jan 3, 2013

oops yeah, probably a 503 would be best

@ajostergaard

Any idea how to detect an actual 408? What should I trigger off?

@tj
Sencha Labs member
tj commented Jan 3, 2013

effectively the same way we're doing things here just for the read end instead

@tj tj added a commit that closed this issue Jan 3, 2013
@tj tj change `timeout()` 408 to 503
seems more appropriate. Closes #719
3f473e5
@tj tj closed this in 3f473e5 Jan 3, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment