You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Marc Slemko <ma...@znep.com> on 1998/07/31 19:19:12 UTC
general/2751: Handler problem false, should not be logged. (fwd)
The new way of doing these is broken because it logs an error before
wildcard handlers have a chance. I have trouble figuring out what
the intent was there, since it obviously makes wildcard handlers
"useless" if that were to be the right behaviour.
---------- Forwarded message ----------
Date: 31 Jul 1998 16:21:01 -0000
From: Darrell Schulte <ds...@facstaff.wisc.edu>
To: apbugs@hyperreal.org
Subject: general/2751: Handler problem false, should not be logged.
>Number: 2751
>Category: general
>Synopsis: Handler problem false, should not be logged.
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri Jul 31 09:30:00 PDT 1998
>Last-Modified:
>Originator: dschulte@facstaff.wisc.edu
>Organization:
apache
>Release: 1.3.1
>Environment:
Linux news2.news.wisc.edu 2.0.34 #10 Sun Jun 14 12:57:01 EDT 1998 i686 unknown
No extra modules.
gcc version 2.7.2.3
>Description:
Followup to #2584, July 10 and #2529, June 30.
I noticed that I was getting a similiar logging info in comparision with #2584.
[Fri Jul 31 10:49:15 1998] [notice] Apache/1.3.1 (Unix) configured -- resuming normal operations
[Fri Jul 31 10:49:30 1998] [warn] handler "msql" not found for: /home/httpd/html/test.msql
[Fri Jul 31 10:49:32 1998] [error] File does not exist: /home/httpd/html/yes.html
[Fri Jul 31 10:49:56 1998] [warn] handler "msql" not found for: /home/httpd/html/index.msql
[Fri Jul 31 10:49:57 1998] [error] File does not exist: /home/httpd/html/yes.html
srm.conf includes:
DirectoryIndex index.msql index.html
AddHandler msql .msql
Action msql /cgi-bin/w3-msql
This setup matches another box running Apache 1.2.6 and which doesn't show this log
behavior.
For testing, I changed access.conf:
from
Options Indexes FollowSymLinks Includes
to
Options Indexes FollowSymLinks
[reference #2529]
No change, as these seemingly "bogus" warnings still appear in the log.
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
Re: general/2751: Handler problem false, should not be logged. (fwd)
Posted by Marc Slemko <ma...@worldgate.com>.
Hmm. Ok, I see the (my) confusion.
Technically, you shouldn't AddHandler for an Action script you should
AddType. But the implicit assumption is that a */* content type handler
will get anything that may have a specific handler handler (which makes
sense) and can then take action on it.
The problem is that means that even if we don't have any "*"s, a "*/*" can
still do something with a handler even though it is only getting things
based on content type; that is the way mod_actions works. Is it
technically correct? All a matter of definitions.
On Fri, 31 Jul 1998, Alexei Kosut wrote:
> On Fri, 31 Jul 1998, Dean Gaudet wrote:
>
> > Isn't it only * handlers we need to worry about? */* should only apply to
> > content types, not r->handler.
>
> I agree. */* should only apply to content types, since handlers don't have
> slashes. Although, IIRC, the current code only checks to see if the first
> character is *, and presumes */* from that.
>
> It should be fixed, and it should be simple to fix, but not trivial.
>
> -- Alexei Kosut <ak...@stanford.edu> <http://www.stanford.edu/~akosut/>
> Stanford University, Class of 2001 * Apache <http://www.apache.org> *
>
>
Re: general/2751: Handler problem false, should not be logged. (fwd)
Posted by Dean Gaudet <dg...@arctic.org>.
On Fri, 31 Jul 1998, Alexei Kosut wrote:
> On Fri, 31 Jul 1998, Dean Gaudet wrote:
>
> > Isn't it only * handlers we need to worry about? */* should only apply to
> > content types, not r->handler.
>
> I agree. */* should only apply to content types, since handlers don't have
> slashes. Although, IIRC, the current code only checks to see if the first
> character is *, and presumes */* from that.
No it actually uses strchr(foo, '*'). But it lets * wildcard to anything,
including /.
Dean
Re: general/2751: Handler problem false, should not be logged. (fwd)
Posted by Alexei Kosut <ak...@leland.Stanford.EDU>.
On Fri, 31 Jul 1998, Dean Gaudet wrote:
> Isn't it only * handlers we need to worry about? */* should only apply to
> content types, not r->handler.
I agree. */* should only apply to content types, since handlers don't have
slashes. Although, IIRC, the current code only checks to see if the first
character is *, and presumes */* from that.
It should be fixed, and it should be simple to fix, but not trivial.
-- Alexei Kosut <ak...@stanford.edu> <http://www.stanford.edu/~akosut/>
Stanford University, Class of 2001 * Apache <http://www.apache.org> *
Re: general/2751: Handler problem false, should not be logged. (fwd)
Posted by Dean Gaudet <dg...@arctic.org>.
Isn't it only * handlers we need to worry about? */* should only apply to
content types, not r->handler.
Dean
On Fri, 31 Jul 1998, Marc Slemko wrote:
> I guess we just have to remove it. Too bad, it was a useful error.
>
> Otherwise any */* handler can decide if it should or shouldn't handle it
> based on arbitrary data, so we can't ever log it if there is any */*
> handler present. I guess that could work, since mod_actions is the only
> */* hander we distribute aside from default_handler. Means some special
> casing of default_handler though.
>
> On Fri, 31 Jul 1998, Dean Gaudet wrote:
>
> > Then fix it... I'm sorry I didn't notice this other bug.
> >
> > Dean
> >
> > On Fri, 31 Jul 1998, Marc Slemko wrote:
> >
> > > Yes, it was broken but should have been fixed properly...
> > >
> > > On Fri, 31 Jul 1998, Dean Gaudet wrote:
> > >
> > > > Look at the PR that lead to the new behaviour, because the old behaviour
> > > > was also broken.
>
>
Re: general/2751: Handler problem false, should not be logged. (fwd)
Posted by Marc Slemko <ma...@worldgate.com>.
I guess we just have to remove it. Too bad, it was a useful error.
Otherwise any */* handler can decide if it should or shouldn't handle it
based on arbitrary data, so we can't ever log it if there is any */*
handler present. I guess that could work, since mod_actions is the only
*/* hander we distribute aside from default_handler. Means some special
casing of default_handler though.
On Fri, 31 Jul 1998, Dean Gaudet wrote:
> Then fix it... I'm sorry I didn't notice this other bug.
>
> Dean
>
> On Fri, 31 Jul 1998, Marc Slemko wrote:
>
> > Yes, it was broken but should have been fixed properly...
> >
> > On Fri, 31 Jul 1998, Dean Gaudet wrote:
> >
> > > Look at the PR that lead to the new behaviour, because the old behaviour
> > > was also broken.
Re: general/2751: Handler problem false, should not be logged. (fwd)
Posted by Dean Gaudet <dg...@arctic.org>.
Then fix it... I'm sorry I didn't notice this other bug.
Dean
On Fri, 31 Jul 1998, Marc Slemko wrote:
> Yes, it was broken but should have been fixed properly...
>
> On Fri, 31 Jul 1998, Dean Gaudet wrote:
>
> > Look at the PR that lead to the new behaviour, because the old behaviour
> > was also broken.
> >
> > Dean
> >
> > On Fri, 31 Jul 1998, Marc Slemko wrote:
> >
> > > The new way of doing these is broken because it logs an error before
> > > wildcard handlers have a chance. I have trouble figuring out what
> > > the intent was there, since it obviously makes wildcard handlers
> > > "useless" if that were to be the right behaviour.
> > >
> > > ---------- Forwarded message ----------
> > > Date: 31 Jul 1998 16:21:01 -0000
> > > From: Darrell Schulte <ds...@facstaff.wisc.edu>
> > > To: apbugs@hyperreal.org
> > > Subject: general/2751: Handler problem false, should not be logged.
> > >
> > >
> > > >Number: 2751
> > > >Category: general
> > > >Synopsis: Handler problem false, should not be logged.
> > > >Confidential: no
> > > >Severity: non-critical
> > > >Priority: medium
> > > >Responsible: apache
> > > >State: open
> > > >Class: sw-bug
> > > >Submitter-Id: apache
> > > >Arrival-Date: Fri Jul 31 09:30:00 PDT 1998
> > > >Last-Modified:
> > > >Originator: dschulte@facstaff.wisc.edu
> > > >Organization:
> > > apache
> > > >Release: 1.3.1
> > > >Environment:
> > > Linux news2.news.wisc.edu 2.0.34 #10 Sun Jun 14 12:57:01 EDT 1998 i686 unknown
> > > No extra modules.
> > > gcc version 2.7.2.3
> > > >Description:
> > > Followup to #2584, July 10 and #2529, June 30.
> > > I noticed that I was getting a similiar logging info in comparision with #2584.
> > >
> > > [Fri Jul 31 10:49:15 1998] [notice] Apache/1.3.1 (Unix) configured -- resuming normal operations
> > > [Fri Jul 31 10:49:30 1998] [warn] handler "msql" not found for: /home/httpd/html/test.msql
> > > [Fri Jul 31 10:49:32 1998] [error] File does not exist: /home/httpd/html/yes.html
> > > [Fri Jul 31 10:49:56 1998] [warn] handler "msql" not found for: /home/httpd/html/index.msql
> > > [Fri Jul 31 10:49:57 1998] [error] File does not exist: /home/httpd/html/yes.html
> > >
> > > srm.conf includes:
> > > DirectoryIndex index.msql index.html
> > > AddHandler msql .msql
> > > Action msql /cgi-bin/w3-msql
> > >
> > > This setup matches another box running Apache 1.2.6 and which doesn't show this log
> > > behavior.
> > >
> > > For testing, I changed access.conf:
> > > from
> > > Options Indexes FollowSymLinks Includes
> > > to
> > > Options Indexes FollowSymLinks
> > >
> > > [reference #2529]
> > >
> > > No change, as these seemingly "bogus" warnings still appear in the log.
> > > >How-To-Repeat:
> > >
> > > >Fix:
> > >
> > > >Audit-Trail:
> > > >Unformatted:
> > > [In order for any reply to be added to the PR database, ]
> > > [you need to include <ap...@Apache.Org> in the Cc line ]
> > > [and leave the subject line UNCHANGED. This is not done]
> > > [automatically because of the potential for mail loops. ]
> > >
> > >
> > >
> > >
> >
>
>
Re: general/2751: Handler problem false, should not be logged. (fwd)
Posted by Marc Slemko <ma...@worldgate.com>.
Yes, it was broken but should have been fixed properly...
On Fri, 31 Jul 1998, Dean Gaudet wrote:
> Look at the PR that lead to the new behaviour, because the old behaviour
> was also broken.
>
> Dean
>
> On Fri, 31 Jul 1998, Marc Slemko wrote:
>
> > The new way of doing these is broken because it logs an error before
> > wildcard handlers have a chance. I have trouble figuring out what
> > the intent was there, since it obviously makes wildcard handlers
> > "useless" if that were to be the right behaviour.
> >
> > ---------- Forwarded message ----------
> > Date: 31 Jul 1998 16:21:01 -0000
> > From: Darrell Schulte <ds...@facstaff.wisc.edu>
> > To: apbugs@hyperreal.org
> > Subject: general/2751: Handler problem false, should not be logged.
> >
> >
> > >Number: 2751
> > >Category: general
> > >Synopsis: Handler problem false, should not be logged.
> > >Confidential: no
> > >Severity: non-critical
> > >Priority: medium
> > >Responsible: apache
> > >State: open
> > >Class: sw-bug
> > >Submitter-Id: apache
> > >Arrival-Date: Fri Jul 31 09:30:00 PDT 1998
> > >Last-Modified:
> > >Originator: dschulte@facstaff.wisc.edu
> > >Organization:
> > apache
> > >Release: 1.3.1
> > >Environment:
> > Linux news2.news.wisc.edu 2.0.34 #10 Sun Jun 14 12:57:01 EDT 1998 i686 unknown
> > No extra modules.
> > gcc version 2.7.2.3
> > >Description:
> > Followup to #2584, July 10 and #2529, June 30.
> > I noticed that I was getting a similiar logging info in comparision with #2584.
> >
> > [Fri Jul 31 10:49:15 1998] [notice] Apache/1.3.1 (Unix) configured -- resuming normal operations
> > [Fri Jul 31 10:49:30 1998] [warn] handler "msql" not found for: /home/httpd/html/test.msql
> > [Fri Jul 31 10:49:32 1998] [error] File does not exist: /home/httpd/html/yes.html
> > [Fri Jul 31 10:49:56 1998] [warn] handler "msql" not found for: /home/httpd/html/index.msql
> > [Fri Jul 31 10:49:57 1998] [error] File does not exist: /home/httpd/html/yes.html
> >
> > srm.conf includes:
> > DirectoryIndex index.msql index.html
> > AddHandler msql .msql
> > Action msql /cgi-bin/w3-msql
> >
> > This setup matches another box running Apache 1.2.6 and which doesn't show this log
> > behavior.
> >
> > For testing, I changed access.conf:
> > from
> > Options Indexes FollowSymLinks Includes
> > to
> > Options Indexes FollowSymLinks
> >
> > [reference #2529]
> >
> > No change, as these seemingly "bogus" warnings still appear in the log.
> > >How-To-Repeat:
> >
> > >Fix:
> >
> > >Audit-Trail:
> > >Unformatted:
> > [In order for any reply to be added to the PR database, ]
> > [you need to include <ap...@Apache.Org> in the Cc line ]
> > [and leave the subject line UNCHANGED. This is not done]
> > [automatically because of the potential for mail loops. ]
> >
> >
> >
> >
>
Re: general/2751: Handler problem false, should not be logged. (fwd)
Posted by Dean Gaudet <dg...@arctic.org>.
Look at the PR that lead to the new behaviour, because the old behaviour
was also broken.
Dean
On Fri, 31 Jul 1998, Marc Slemko wrote:
> The new way of doing these is broken because it logs an error before
> wildcard handlers have a chance. I have trouble figuring out what
> the intent was there, since it obviously makes wildcard handlers
> "useless" if that were to be the right behaviour.
>
> ---------- Forwarded message ----------
> Date: 31 Jul 1998 16:21:01 -0000
> From: Darrell Schulte <ds...@facstaff.wisc.edu>
> To: apbugs@hyperreal.org
> Subject: general/2751: Handler problem false, should not be logged.
>
>
> >Number: 2751
> >Category: general
> >Synopsis: Handler problem false, should not be logged.
> >Confidential: no
> >Severity: non-critical
> >Priority: medium
> >Responsible: apache
> >State: open
> >Class: sw-bug
> >Submitter-Id: apache
> >Arrival-Date: Fri Jul 31 09:30:00 PDT 1998
> >Last-Modified:
> >Originator: dschulte@facstaff.wisc.edu
> >Organization:
> apache
> >Release: 1.3.1
> >Environment:
> Linux news2.news.wisc.edu 2.0.34 #10 Sun Jun 14 12:57:01 EDT 1998 i686 unknown
> No extra modules.
> gcc version 2.7.2.3
> >Description:
> Followup to #2584, July 10 and #2529, June 30.
> I noticed that I was getting a similiar logging info in comparision with #2584.
>
> [Fri Jul 31 10:49:15 1998] [notice] Apache/1.3.1 (Unix) configured -- resuming normal operations
> [Fri Jul 31 10:49:30 1998] [warn] handler "msql" not found for: /home/httpd/html/test.msql
> [Fri Jul 31 10:49:32 1998] [error] File does not exist: /home/httpd/html/yes.html
> [Fri Jul 31 10:49:56 1998] [warn] handler "msql" not found for: /home/httpd/html/index.msql
> [Fri Jul 31 10:49:57 1998] [error] File does not exist: /home/httpd/html/yes.html
>
> srm.conf includes:
> DirectoryIndex index.msql index.html
> AddHandler msql .msql
> Action msql /cgi-bin/w3-msql
>
> This setup matches another box running Apache 1.2.6 and which doesn't show this log
> behavior.
>
> For testing, I changed access.conf:
> from
> Options Indexes FollowSymLinks Includes
> to
> Options Indexes FollowSymLinks
>
> [reference #2529]
>
> No change, as these seemingly "bogus" warnings still appear in the log.
> >How-To-Repeat:
>
> >Fix:
>
> >Audit-Trail:
> >Unformatted:
> [In order for any reply to be added to the PR database, ]
> [you need to include <ap...@Apache.Org> in the Cc line ]
> [and leave the subject line UNCHANGED. This is not done]
> [automatically because of the potential for mail loops. ]
>
>
>
>