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/02/25 23:17:23 UTC
Re: other/1872: Problem with configuration file (fwd)
It wouldn't hurt to be more explicit in the CHANGES file than:
*) Correct handling of quotation marks in AuthName realm names; as a
byproduct, a new function: ap_escape_quotes(). [Ken Coar] PR#1195
---------- Forwarded message ----------
Date: 25 Feb 1998 22:00:26 -0000
From: marc@hyperreal.org
To: apache-bugdb@apache.org, marc@apache.org, ned@oolympus.net
Subject: Re: other/1872: Problem with configuration file
Synopsis: Problem with configuration file
State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Wed Feb 25 14:00:23 PST 1998
State-Changed-Why:
Multi-word AuthName settings now have to be enclosed
in double quotes (eg. AuthName "foo bar").
This probably isn't made clear enough in the CHANGES file.
Re: other/1872: Problem with configuration file (fwd)
Posted by Marc Slemko <ma...@worldgate.com>.
On Wed, 25 Feb 1998, Dean Gaudet wrote:
> You mean like (from upgrading to 1.3):
Well yea, but who is the silly person that reads upgrading to 1.3 files?
That should be a _summary_ of _some_ of the more important things in
CHANGES in an easier to digest format, not a replacement.
>
> <LI><STRONG><SAMP>AuthName</SAMP> strings may need to be quoted</STRONG>
> in <SAMP>.htaccess</SAMP> or server configuration files. If you use
> an <SAMP>AuthName</SAMP> directive like this:
> <P>
> <PRE>
> AuthName This and That
> </PRE>
> </P>
> you will need to change it to
> <P>
> <PRE>
> AuthName "This and That"
> </PRE>
> </P>
> This change was made for HTTP/1.1 compliance.
>
> Although I completely disagree with the last line of that.
>
> Dean
>
> On Wed, 25 Feb 1998, Marc Slemko wrote:
>
> > It wouldn't hurt to be more explicit in the CHANGES file than:
> >
> > *) Correct handling of quotation marks in AuthName realm names; as a
> > byproduct, a new function: ap_escape_quotes(). [Ken Coar] PR#1195
> >
> >
> > ---------- Forwarded message ----------
> > Date: 25 Feb 1998 22:00:26 -0000
> > From: marc@hyperreal.org
> > To: apache-bugdb@apache.org, marc@apache.org, ned@oolympus.net
> > Subject: Re: other/1872: Problem with configuration file
> >
> > Synopsis: Problem with configuration file
> >
> > State-Changed-From-To: open-closed
> > State-Changed-By: marc
> > State-Changed-When: Wed Feb 25 14:00:23 PST 1998
> > State-Changed-Why:
> > Multi-word AuthName settings now have to be enclosed
> > in double quotes (eg. AuthName "foo bar").
> >
> > This probably isn't made clear enough in the CHANGES file.
> >
> >
>
Re: other/1872: Problem with configuration file (fwd)
Posted by Dean Gaudet <dg...@arctic.org>.
You mean like (from upgrading to 1.3):
<LI><STRONG><SAMP>AuthName</SAMP> strings may need to be quoted</STRONG>
in <SAMP>.htaccess</SAMP> or server configuration files. If you use
an <SAMP>AuthName</SAMP> directive like this:
<P>
<PRE>
AuthName This and That
</PRE>
</P>
you will need to change it to
<P>
<PRE>
AuthName "This and That"
</PRE>
</P>
This change was made for HTTP/1.1 compliance.
Although I completely disagree with the last line of that.
Dean
On Wed, 25 Feb 1998, Marc Slemko wrote:
> It wouldn't hurt to be more explicit in the CHANGES file than:
>
> *) Correct handling of quotation marks in AuthName realm names; as a
> byproduct, a new function: ap_escape_quotes(). [Ken Coar] PR#1195
>
>
> ---------- Forwarded message ----------
> Date: 25 Feb 1998 22:00:26 -0000
> From: marc@hyperreal.org
> To: apache-bugdb@apache.org, marc@apache.org, ned@oolympus.net
> Subject: Re: other/1872: Problem with configuration file
>
> Synopsis: Problem with configuration file
>
> State-Changed-From-To: open-closed
> State-Changed-By: marc
> State-Changed-When: Wed Feb 25 14:00:23 PST 1998
> State-Changed-Why:
> Multi-word AuthName settings now have to be enclosed
> in double quotes (eg. AuthName "foo bar").
>
> This probably isn't made clear enough in the CHANGES file.
>
>