E63 send as is

[Rob Hartill <ha...@ooo.lanl.gov>]

Patch E63 is at hyperreal, it's a 2 line patch to enable people
to set up a file extension or list of file extensions that Apache
will treat as not wanting server generated HTTP headers to be
attached.

So a file with


HTTP/1.0 302 Now where did I leave that URL
Location: http://xyz.abc.com/foo/bar.html
Content-type: text/html

<HTML>
<HEAD>
<TITLE>Lame excuses'R'us</TITLE>
</HEAD>
<BODY>
<H1>Fred's exceptionally wonderful page has moved to
<A HREF="http://xyz.abc.com/foo/bar.html">Joe's</A> site.
</H1>
</BODY>
</HTML>

Could be written to do a redirect from an ordinary file.


Yummy, yummy

Documentation to follow.

robh

Patch-Submit Form

[Mark J Cox <M....@bradford.ac.uk>]

On Tue, 11 Apr 1995, Brian Behlendorf wrote:
> Mark, the patch-submit form worked fine for me - could you have a browser 
> bug?

It was due to the "Option Value" and an old version of Lynx I was using. See 
http://www.research.digital.com/nsl/formtest/stats-by-test/OptionValue.html

(The form will not work for EI*Net,InternetWorks,Lynx<2.3.1,MacMosaic,
and a few others: I always tend to avoid "option value")

Mark

P67 (was Re: P15 DBM Group File)

[Brian Behlendorf <br...@wired.com>]

In adding this to the patchfile database, it got a patch ID of 67, so 
it's now at patches/for_Apache_0.5.1/P67-patch.new_dbm_group_file.txt

Mark, the patch-submit form worked fine for me - could you have a browser 
bug?

If this works as advertised, it gets a +1 from me.

	Brian

On Tue, 11 Apr 1995, Mark J Cox wrote:
> I've uploaded P15 to hyperreal.  It's a short patch to complement
> the existing DBM password database.
> 
> This patch allows groups to be held in a DBM file in a similar way to
> the password DBM.  You can have any combination of normal password file,
> normal group file, DBM password file, DBM group file.
>  
> A new directive AuthDBMGroupFile is added to the .htaccess processing.
>  
> The group DBM file is keyed on username with a content of
> :comma_separated_group_names
>  
> Thus the entry ":cod,haddock" would give the user entry to group protected
> documents "cod" or "haddock".
>  
> Anything before the initial : and anything after a final : is ignored.  The
> original DBM password patch is modified to ignore anything after a final :.
> Thus the password and group details can be stored in the same DBM file if
> required (the DBM file is opened and examined twice in this case).
>  
>         key=username, content=CryptedPassword:CommaSeparatedGroups:Anything
>  
> Mark
> 
> 
> 

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@hotwired.com  brian@hyperreal.com  http://www.hotwired.com/Staff/brian/

P15 DBM Group File

[Mark J Cox <M....@bradford.ac.uk>]

I've uploaded P15 to hyperreal.  It's a short patch to complement
the existing DBM password database.

This patch allows groups to be held in a DBM file in a similar way to
the password DBM.  You can have any combination of normal password file,
normal group file, DBM password file, DBM group file.
 
A new directive AuthDBMGroupFile is added to the .htaccess processing.
 
The group DBM file is keyed on username with a content of
:comma_separated_group_names
 
Thus the entry ":cod,haddock" would give the user entry to group protected
documents "cod" or "haddock".
 
Anything before the initial : and anything after a final : is ignored.  The
original DBM password patch is modified to ignore anything after a final :.
Thus the password and group details can be stored in the same DBM file if
required (the DBM file is opened and examined twice in this case).
 
        key=username, content=CryptedPassword:CommaSeparatedGroups:Anything
 
Mark

Re: E63 send as is

[Brian Behlendorf <br...@wired.com>]

On Mon, 10 Apr 1995, Rob Hartill wrote:
> Patch E63 is at hyperreal, it's a 2 line patch to enable people
> to set up a file extension or list of file extensions that Apache
> will treat as not wanting server generated HTTP headers to be
> attached.

What will a HEAD request on that document generate?

	Brian

--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@hotwired.com  brian@hyperreal.com  http://www.hotwired.com/Staff/brian/