connect.timeout sends a 408 #719

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

Comments

Projects
None yet
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

This comment has been minimized.

Show comment Hide comment
@tj

tj Jan 3, 2013

Member

oops yeah, probably a 503 would be best

Member

tj commented Jan 3, 2013

oops yeah, probably a 503 would be best

@ajostergaard

This comment has been minimized.

Show comment Hide comment
@ajostergaard

ajostergaard Jan 3, 2013

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

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

@tj

This comment has been minimized.

Show comment Hide comment
@tj

tj Jan 3, 2013

Member

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

Member

tj commented Jan 3, 2013

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

@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