www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From m...@apache.org
Subject Re: general/8222: Unexpected status code in reply to Code Red URL
Date Wed, 22 Aug 2001 16:52:27 GMT
[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: Unexpected status code in reply to Code Red URL

State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Wed Aug 22 09:52:26 PDT 2001
Erm... there are a number of reasons for seeing different status codes, especially when using
very old versions of Apache like 1.3.6.

Note on the 200 responses, the response length is "-".  This means it timed out before sending
the response, due to network issues between the server and client or due to the worm not responding
in a timely matter for whatever reason... if you were using a current version of Apache, you
would see a timed-out status code there.

As for the 400, there are a variety of reasons why this can happen.  There are a lot of different
parts of the request other  than what is logged in the access log... namely, some code red
variants send a bogus Host: header.

In short, there really isn't anything to worry about here or any bug in (current versions
of!) Apache.  

View raw message