apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: blocking bucket reads on non-blocking sockets
Date Sat, 15 May 2004 00:36:01 GMT
Joe Orton wrote:
> On Fri, May 14, 2004 at 04:16:34PM -0700, Stas Bekman wrote:
>>Cliff Woolley wrote:
>>>On Fri, 14 May 2004, Stas Bekman wrote:
>>>>So, who changed that in 2.0.49? It worked just fine pre-2.0.48. The
>>>>guilty party please stand up and explain. This change causes a
>>>>serious breakage in the protocol handlers and filters on those
>>>>affected platforms. I suppose apr doesn't have tests for that, and
>>>>that's why the problem wasn't caught when it was introduced. Thanks.
> Oh, the trigger for this is as we discussed before, simply the fact that
> 2.0.49 leaves sockets with O_NONBLOCK set (after the multi-listen DoS
> security fix) on some platforms.

Was this fix needed specificaly for HTTP or for any protocols?

> This doesn't matter for httpd since any request-level filters will use
> the apr_socket when it has a non-zero timeout set (by the net_time
> filter), in which case it acts just like a blocking socket.
> The problem is as you say in protocol-level filters/handlers; there, the
> apr_socket has no timeout set, so it really does act like a non-blocking
> socket.

So what's the solution here?

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

View raw message