www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Kelley <ben_kel...@wdr.com>
Subject mod_jserv/4790: ajp11: cannot scan servlet headers in mod_jserv.log
Date Thu, 29 Jul 1999 08:09:54 GMT

>Number:         4790
>Category:       mod_jserv
>Synopsis:       ajp11: cannot scan servlet headers in mod_jserv.log
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    jserv
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jul 29 01:10:01 PDT 1999
>Last-Modified:
>Originator:     ben_kelley@wdr.com
>Organization:
apache
>Release:        1.3.6 Jserv 1.0
>Environment:
Solaris 2.5.1, gcc 2.6.3
>Description:
On loading some servlets, this error message appears in mod_jserv.log. The
browser is returned a page telling it an error has occurred. The statis is
200, and the error is "OK".

It seems to happen more often when reloading a servlet than when fetching it
initially.

Sometimes it happens, sometimes it doesn't. This is not a terribly useful
error message - a response to a previous bug report suggested looking in
the source code to find the reason.

Scanning the source seems to point to the error being generated from the
funtion compat_scan_script_header_err_buff in jserv_compat.c (in mod_jserv).

The call to "log_reason (malformed, r->filename, r)" would seem to log the
reason it thinks that headers are malformed, but the output of this does not
seem to appear anywhere.

Interestingly, the servlet that reports this error most often worked fine with
the 0.9 release of mod_jserv. The headers it reports back (assuming you can
fetch it) are below. It returns an Expires: header, and a Last-Modified: header.

HTTP/1.1 200 OK
Date: Thu, 29 Jul 1999 08:07:30 GMT
Server: Apache/1.3.6 (Unix) ApacheJServ/1.0
Expires: Fri, 30 Jul 1999 08:07:32 GMT
Last-Modified: Wed, 28 Jul 1999 00:13:53 GMT
Connection: close
Content-Type: text/html
>How-To-Repeat:

>Fix:

>Audit-Trail:
>Unformatted:
[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!     ]




Mime
View raw message