httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41796] New: - Internal Dummy Connection should process effortlessly
Date Fri, 09 Mar 2007 01:49:06 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41796>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=41796

           Summary: Internal Dummy Connection should process effortlessly
           Product: Apache httpd-2
           Version: 2.2.3
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: prefork
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: phyre@rogers.com


It's clear that the Internal Dummy Connection requests are needed and it is my
understanding that these exist in 2.0 but however are not logged.

My concern is not with them existing or logging, but with the request that is
being made.
The "GET /" request used causes dynamic pages to generate- in some cases with
tens or hundreds of requests in a matter of a few seconds.  A dynamic page I
have shows these Internal dummy connections making tens of database queries to
generate and returning 100-200KB of data to the dummy connection.

This should be changed to either:
 a) request something else other than "GET /", such as using "OPTIONS *", or
"GET /robots.txt" or "GET /apache_internal_dummy_file.txt" that would not be
used or would not incur the massive processing of many of today's Web sites.
 -OR- (better yet)
 b) be handled specially by the request handler that in the case of a connection
from the local IP with that user agent, it should avoid as much advanced
processing as possible(rewrite rules, PHP scripts, Perl scripts, SSI, Directory
restrictions, htaccess processing, etc), and simply return a very short "ACK"
style request with only the necessary headers to be deemed valid.

When the whole server approaches the request limit near the same time or
receives certain commands that dispatch these, it is important that it is not
making requests it shouldn't.

Advertisers and users depend on these database requests to count pageviews and
other measures that Apache suddenly adds hundreds of throughout a day... which
can add up and show a difference in pageviews from what actually is occuring.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message