www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davey Silon" <dav...@holycamel.com>
Subject RE: general/8625: Redirect Command In .htaccess Drops Concurrent Requests From The Same Client
Date Mon, 29 Oct 2001 16:50:00 GMT
The following reply was made to PR general/8625; it has been noted by GNATS.

From: "Davey Silon" <daveys@holycamel.com>
To: <slive@apache.org>
Cc: <apbugs@apache.org>
Subject: RE: general/8625: Redirect Command In .htaccess Drops Concurrent Requests From The
Same Client
Date: Mon, 29 Oct 2001 08:45:04 -0800

 Thanks for the reply. I understand the inherent nature of the worm URLs I
 was sending.  However, the point of using redirect is to reduce bandwidth
 served by our servers, which have gotten literally thousands of badly-formed
 worm requests.  Not serving pages like a 404 or 400 page for those requests
 will save bandwidth.
 I have been able to reproduce the problem with a single request from a URL
 line using the log entries I sent (for the 400 or 404's).  Apache's string
 matching shouldn't fail, no matter what the circumstance, as long as the
 match string is present.  That is currently not the case.  Whatever
 expression matching Apache is using is obviously not sufficiently robust,
 since the Redirect is not working.  The source of the request shouldn't
 matter - worm or not.  The redirect expression matching is failing, and that
 should be cause enough for action.  String matching problems are some of the
 easiest ones to fix and if it improves overall robustness, it's a good
 Also, by the way, it would be nice to be able to selectively omit those
 requests from the log.  My server logs are a mess.  I want to leave them set
 to the warn level, but Apache really needs an "OmitLog" directive that does
 the same thing that Redirect does to prevent specific accesses from clogging
 the logs with unwanted garbage, impairing their effectiveness.
 I really love Apache and think it is a great product.  Fixing redirect and
 adding an OmitLog command would really help make it impervious to stupid
 MS-based worms.  If there is some way to accomplish the OmitLog function in
 the current version, I'd love to know.
 Thanks for taking the time to reply.  I apreciate your help.  I know you
 guys must be busy, but I think in the current climate with MS Worms, these
 are very worthy bugs to address to improve server performance.
 Davey Silon
 -----Original Message-----
 From: slive@apache.org [mailto:slive@apache.org]
 Sent: Monday, October 29, 2001 7:09 AM
 To: apache-bugdb@apache.org; daveys@holycamel.com; slive@apache.org
 Subject: Re: general/8625: Redirect Command In .htaccess Drops
 Concurrent Requests From The Same Client
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 Synopsis: Redirect Command In .htaccess Drops Concurrent Requests From The
 Same Client
 State-Changed-From-To: open-closed
 State-Changed-By: slive
 State-Changed-When: Mon Oct 29 07:09:27 PST 2001
 This is not a good way to test Redirect.  The worm is throwing requests that
 are deliberately designed to foul up request parsing.  Some of them are
 getting 400 (Bad request) responses, which is perfectly legitimate.  The
 ones that are getting 404 responses are probably correct also, although I'm
 not going to take the time to decompose that absurd URL according the the
 RFC rules.
 If you can generate this problem with any real client sending real requests,
 please let us know.  Otherwise, you are really just wasting your time by
 sending redirects to a worm.  There is no way they will be followed.
 Thanks for using Apache!

View raw message