[Mongrel-development] Small updates and release plan

Luis Lavena
Tue, 11 Dec 2007 02:00:16 -0000

On Dec 10, 2007 10:22 PM, Filipe <filipe at icewall.org>
wrote:
>
> Who invited this Zed-guy to the list? He is just spreading FUD around here
:)
>

Zed was the owner of the circus, we are just pets on the show ;-)

> Anyway, the return code is defined in [1]. you know, it''s not
because
> your code works right(TM) that all code in the world will work ok
> too... and implementing this even clients will display the correct
> HTML code.
>
> 1. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1
>

A bit above that:

Quote:

10.4 Client Error 4xx

The 4xx class of status code is intended for cases in which the client
seems to have erred. Except when responding to a HEAD request, the
server SHOULD include an entity containing an explanation of the error
situation, and whether it is a temporary or permanent condition. These
status codes are applicable to any request method. User agents SHOULD
display any included entity to the user.

=
As Zed commented, a client, not a proxy.

Quote:

If the client is sending data, a server implementation using TCP
SHOULD be careful to ensure that the client acknowledges receipt of
the packet(s) containing the response, before the server closes the
input connection. If the client continues sending data to the server
after the close, the server''s TCP stack will send a reset packet to
the client, which may erase the client''s unacknowledged input buffers
before they can be read and interpreted by the HTTP application.

==
Again, I''ll *love* to know how apache or any other balancer handle
this edge case.

(with love I mean, more feedback besides nginx) :-D

--
Luis Lavena
Multimedia systems
-
A common mistake that people make when trying to design
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams