You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@httpd.apache.org by Joshua Slive <sl...@finance.commerce.ubc.ca> on 2000/12/17 21:35:01 UTC
Urgent 2.0 issues
These are the things that I think really need to be done pronto with the
2.0 docs. More details are in the STATUS file in the repository.
1. Installation docs: I can't even compile the most recent alpha on any of
my systems, so I am at a loss on how to even start this.
2. Filters: I think we need some advice from Ryan here. I don't
understand what the user interface to filters is supposed to be. How are
documents supposed to be designated for SSI processing, for example?
3. Website: I believe it is time to place the 2.0 docs on the website
in a similar manner to the 1.3 docs. I don't have the karma to do this
myself.
Beyond that, I am not sure what the state of the XHTML conversion is.
Several people have volunteered to help out, but I guess nobody wants to
lead the charge.
Joshua.
Re: Urgent 2.0 issues
Posted by Joshua Slive <sl...@finance.commerce.ubc.ca>.
On Sun, 17 Dec 2000 rbb@covalent.net wrote:
>
> I'll try to look at the STATUS file today, but I am focused on a few known
> bugs that I want to get rid of ASAP, so it may take me a little while.
No problem. Thanks for the info. I have a problem with the filter stuff
which I will address in a new thread to new-httpd.
Joshua.
Re: Filter interface (was Re: Urgent 2.0 issues)
Posted by Joshua Slive <sl...@finance.commerce.ubc.ca>.
On Sun, 17 Dec 2000 rbb@covalent.net wrote:
> There is no way to distinguish a filter-name from an extension. We could
> search for the filter, and if it isn't known by the server, then we treat
> it as an extension, but that means we can't output errors for incorrent
> filters.
Yah, I didn't think of the error reporting issue.
>
> I prefer this:
>
> SetFilterStack filter_stack_name filter-name [filter-name]
>
> AddFilter filter_stack_name extension
> SetFilter filter_stack_name
>
OK. More complicated than I would like, but I guess it will do.
How about if AddFilter and SetFilter can either take a single filter name
(for the most common cases) or a filter_stack_name?
>
> I do not believe that setting filters based on MIME-type is worthwhile to
> do personally, so I believe that those two options will take care of
> everything we really care about.
>
I guess the only reason for this would be to let CGI scripts determine
their filter stacks dynamically. I have no opinion in either direction.
> Thoughts? If we decide to do this, then it will be implemented before the
> beta.
One more question: How do things interact when multiple
AddFilter/SetFilter directives occur. Is this possible:
<Directory />
SetFilter CACHE
</Directory>
<Directory /www>
SetFilter SSI
</Directory>
Will that result in a filter chain of "SSI CACHE" in the /www directory?
Should it?
Joshua.
Re: Filter interface (was Re: Urgent 2.0 issues)
Posted by rb...@covalent.net.
> I believe this is inconsistent with existing Apache behaviour and should
> be fixed (preferably before the beta). In particular, I suggest that the
> Filter directives be made analagous to the Handler directives. Currently,
> they conflict horribly and we will be confusing people.
>
> My proposal is:
>
> AddFilter
> Similar to AddHandler:
> Syntax: AddFilter filter-name [filter-name] ... extension [extension] ...
>
> SetFilter
> Similar to SetHandler:
> Syntax: SetFilter filter-name [filter-name] ...
>
> FilterByType (or some other similar name)
> Similar to your current SetFilter:
> Syntax: Setfilter filter-name [filter-name] ... MIME-type
There is no way to distinguish a filter-name from an extension. We could
search for the filter, and if it isn't known by the server, then we treat
it as an extension, but that means we can't output errors for incorrent
filters.
I prefer this:
SetFilterStack filter_stack_name filter-name [filter-name]
AddFilter filter_stack_name extension
SetFilter filter_stack_name
I do not believe that setting filters based on MIME-type is worthwhile to
do personally, so I believe that those two options will take care of
everything we really care about.
Thoughts? If we decide to do this, then it will be implemented before the
beta.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Filter interface (was Re: Urgent 2.0 issues)
Posted by Joshua Slive <sl...@finance.commerce.ubc.ca>.
[cross-posted from a discussion on apache-docs]
On Sun, 17 Dec 2000 rbb@covalent.net wrote:
> > 2. Filters: I think we need some advice from Ryan here. I don't
> > understand what the user interface to filters is supposed to be. How are
> > documents supposed to be designated for SSI processing, for example?
>
> Currently, there are two ways to designate a page for filters. The first
> is AddFilter. This is a simple directive that just takes a list of
> filters. SSI's would be enabled for filters by adding the following:
>
> <Files ~ \.shtml$>
> AddFilter INCLUDES
> </Files>
>
> The second is SetFilter. This takes a mime-type and a list of
> filters. So it would look like:
>
> SetFilter test/html INCLUDES
>
I believe this is inconsistent with existing Apache behaviour and should
be fixed (preferably before the beta). In particular, I suggest that the
Filter directives be made analagous to the Handler directives. Currently,
they conflict horribly and we will be confusing people.
My proposal is:
AddFilter
Similar to AddHandler:
Syntax: AddFilter filter-name [filter-name] ... extension [extension] ...
SetFilter
Similar to SetHandler:
Syntax: SetFilter filter-name [filter-name] ...
FilterByType (or some other similar name)
Similar to your current SetFilter:
Syntax: Setfilter filter-name [filter-name] ... MIME-type
Admittedly, this is not perfect, because Apache will need to
check each argument to see whether it is a (for example) extension or
filter-name. Users could assure that a certain argument was processed as
an extension by using the leading dot. The same problem doesn't exist for
MIME-types as long as filter-names cannot contain "/".
And yes, I agree that if we were starting today from scratch, the
AddFilter/AddHandler would not even be necessary because of the use of
<Files> blocks. In addition "SetFilter" will be a misnomer, because it
will actually be "Adding" filters to the stack. However, I think this is
better than corrupting the current usage of these terms.
If you do not agree with this, then PLEASE, at least change the current
AddFilter to be SetFilter and rename the current SetFilter to something
else.
Joshua.
Re: Urgent 2.0 issues
Posted by rb...@covalent.net.
I'll try to apply these tonight.
Ryan
On Mon, 18 Dec 2000, Joshua Slive wrote:
> Ryan,
>
> Here is my suggestion for a change to incorporate the 2.0 docs in the
> website. Along with that small change, I also made two other fixes in the
> index.html page:
>
> 1. Added a missing period in the Apache 2.0 announcement.
>
> 2. Commented out the mirror link, since httpd.apache.org is not mirrored.
>
> Before applying, you just need to check out
> httpd-2.0/docs/manual/ into
> /www/httpd-site/docs-2.0/
>
> Index: index.html
> ===================================================================
> RCS file: /home/cvs/httpd-site/index.html,v
> retrieving revision 1.106
> diff -u -d -b -r1.106 index.html
> --- index.html 2000/10/31 21:19:34 1.106
> +++ index.html 2000/12/18 22:09:11
> @@ -19,8 +19,9 @@
> <H2>Welcome to the Apache HTTP Server Project</H2>
> <H4>A Project of the <a href="http://www.apache.org/"
> >Apache Software Foundation</A></H4>
> -<h3><a href="http://www.apache.org/dyn/closer.cgi">
> -Mirrored worldwide - find your closest mirror</A></H3>
> +
> +<!-- <h3><a href="http://www.apache.org/dyn/closer.cgi">
> +Mirrored worldwide - find your closest mirror</A></H3> -->
>
> <TABLE>
> <TR>
> @@ -28,7 +29,8 @@
> <UL>
> <LI><A HREF="ABOUT_APACHE.html">About the Apache HTTP Server
> Project</A>
> <LI><A HREF="http://www.apache.org/LICENSE.txt">The Apache License</A>
> - <LI><A HREF="docs/">Apache HTTP Server Documentation</A>
> + <LI>Documentation: <A HREF="docs/">Version 1.3</A> |
> + <a href="docs-2.0/">Version 2.0</a>
> <LI><A HREF="docs/misc/FAQ.html">The Apache HTTP Server FAQ</A>
> <LI><A HREF="http://www.apache.org/awards.html">Awards won by the
> Apache software</A>
> <LI><A HREF="bug_report.html">Bug Reporting</A>
> @@ -97,7 +99,7 @@
> which includes several new enhancements, including the new Apache
> Portable
> Run-time, the new Multi-processing modules, and I/O filtering. This is
> an
> alpha release, and is for experimental purposes; use at your own risk. It
> -is available in source format only, so a compiler is neccessary to use it
> +is available in source format only, so a compiler is neccessary to use
> it.
>
> <p>If you are not familiar with software development, and wish to use
> a stable, working, web server, we strongly recommend you download
> @@ -108,7 +110,7 @@
>
> <P ALIGN="CENTER">
> <A HREF="dist/">Download Apache 2.0a7</A> |
> -<A HREF="docs/new_features_2_0.html">New Features in Apache 2.0</A> |
> +<A HREF="docs-2.0/new_features_2_0.html">New Features in Apache 2.0</A> |
> <A HREF="dist/CHANGES_2.0a">ChangeLog for Alpha7</a>
>
> <P><HR>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
> For additional commands, e-mail: apache-docs-help@apache.org
>
>
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: Urgent 2.0 issues
Posted by rb...@covalent.net.
Applied. Thanks. :-)
Ryan
On Mon, 18 Dec 2000, Joshua Slive wrote:
> Ryan,
>
> Here is my suggestion for a change to incorporate the 2.0 docs in the
> website. Along with that small change, I also made two other fixes in the
> index.html page:
>
> 1. Added a missing period in the Apache 2.0 announcement.
>
> 2. Commented out the mirror link, since httpd.apache.org is not mirrored.
>
> Before applying, you just need to check out
> httpd-2.0/docs/manual/ into
> /www/httpd-site/docs-2.0/
>
> Index: index.html
> ===================================================================
> RCS file: /home/cvs/httpd-site/index.html,v
> retrieving revision 1.106
> diff -u -d -b -r1.106 index.html
> --- index.html 2000/10/31 21:19:34 1.106
> +++ index.html 2000/12/18 22:09:11
> @@ -19,8 +19,9 @@
> <H2>Welcome to the Apache HTTP Server Project</H2>
> <H4>A Project of the <a href="http://www.apache.org/"
> >Apache Software Foundation</A></H4>
> -<h3><a href="http://www.apache.org/dyn/closer.cgi">
> -Mirrored worldwide - find your closest mirror</A></H3>
> +
> +<!-- <h3><a href="http://www.apache.org/dyn/closer.cgi">
> +Mirrored worldwide - find your closest mirror</A></H3> -->
>
> <TABLE>
> <TR>
> @@ -28,7 +29,8 @@
> <UL>
> <LI><A HREF="ABOUT_APACHE.html">About the Apache HTTP Server
> Project</A>
> <LI><A HREF="http://www.apache.org/LICENSE.txt">The Apache License</A>
> - <LI><A HREF="docs/">Apache HTTP Server Documentation</A>
> + <LI>Documentation: <A HREF="docs/">Version 1.3</A> |
> + <a href="docs-2.0/">Version 2.0</a>
> <LI><A HREF="docs/misc/FAQ.html">The Apache HTTP Server FAQ</A>
> <LI><A HREF="http://www.apache.org/awards.html">Awards won by the
> Apache software</A>
> <LI><A HREF="bug_report.html">Bug Reporting</A>
> @@ -97,7 +99,7 @@
> which includes several new enhancements, including the new Apache
> Portable
> Run-time, the new Multi-processing modules, and I/O filtering. This is
> an
> alpha release, and is for experimental purposes; use at your own risk. It
> -is available in source format only, so a compiler is neccessary to use it
> +is available in source format only, so a compiler is neccessary to use
> it.
>
> <p>If you are not familiar with software development, and wish to use
> a stable, working, web server, we strongly recommend you download
> @@ -108,7 +110,7 @@
>
> <P ALIGN="CENTER">
> <A HREF="dist/">Download Apache 2.0a7</A> |
> -<A HREF="docs/new_features_2_0.html">New Features in Apache 2.0</A> |
> +<A HREF="docs-2.0/new_features_2_0.html">New Features in Apache 2.0</A> |
> <A HREF="dist/CHANGES_2.0a">ChangeLog for Alpha7</a>
>
> <P><HR>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: apache-docs-unsubscribe@apache.org
> For additional commands, e-mail: apache-docs-help@apache.org
>
>
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: Urgent 2.0 issues
Posted by Joshua Slive <sl...@finance.commerce.ubc.ca>.
Ryan,
Here is my suggestion for a change to incorporate the 2.0 docs in the
website. Along with that small change, I also made two other fixes in the
index.html page:
1. Added a missing period in the Apache 2.0 announcement.
2. Commented out the mirror link, since httpd.apache.org is not mirrored.
Before applying, you just need to check out
httpd-2.0/docs/manual/ into
/www/httpd-site/docs-2.0/
Index: index.html
===================================================================
RCS file: /home/cvs/httpd-site/index.html,v
retrieving revision 1.106
diff -u -d -b -r1.106 index.html
--- index.html 2000/10/31 21:19:34 1.106
+++ index.html 2000/12/18 22:09:11
@@ -19,8 +19,9 @@
<H2>Welcome to the Apache HTTP Server Project</H2>
<H4>A Project of the <a href="http://www.apache.org/"
>Apache Software Foundation</A></H4>
-<h3><a href="http://www.apache.org/dyn/closer.cgi">
-Mirrored worldwide - find your closest mirror</A></H3>
+
+<!-- <h3><a href="http://www.apache.org/dyn/closer.cgi">
+Mirrored worldwide - find your closest mirror</A></H3> -->
<TABLE>
<TR>
@@ -28,7 +29,8 @@
<UL>
<LI><A HREF="ABOUT_APACHE.html">About the Apache HTTP Server
Project</A>
<LI><A HREF="http://www.apache.org/LICENSE.txt">The Apache License</A>
- <LI><A HREF="docs/">Apache HTTP Server Documentation</A>
+ <LI>Documentation: <A HREF="docs/">Version 1.3</A> |
+ <a href="docs-2.0/">Version 2.0</a>
<LI><A HREF="docs/misc/FAQ.html">The Apache HTTP Server FAQ</A>
<LI><A HREF="http://www.apache.org/awards.html">Awards won by the
Apache software</A>
<LI><A HREF="bug_report.html">Bug Reporting</A>
@@ -97,7 +99,7 @@
which includes several new enhancements, including the new Apache
Portable
Run-time, the new Multi-processing modules, and I/O filtering. This is
an
alpha release, and is for experimental purposes; use at your own risk. It
-is available in source format only, so a compiler is neccessary to use it
+is available in source format only, so a compiler is neccessary to use
it.
<p>If you are not familiar with software development, and wish to use
a stable, working, web server, we strongly recommend you download
@@ -108,7 +110,7 @@
<P ALIGN="CENTER">
<A HREF="dist/">Download Apache 2.0a7</A> |
-<A HREF="docs/new_features_2_0.html">New Features in Apache 2.0</A> |
+<A HREF="docs-2.0/new_features_2_0.html">New Features in Apache 2.0</A> |
<A HREF="dist/CHANGES_2.0a">ChangeLog for Alpha7</a>
<P><HR>
Re: Urgent 2.0 issues
Posted by rb...@covalent.net.
> 1. Installation docs: I can't even compile the most recent alpha on any of
> my systems, so I am at a loss on how to even start this.
To compile the most recent alpha, just remove the test target from all
Makefiles. This is an issue that we are aware of. :-( The installation
docs should be very close to the 1.3 installation docs.
> 2. Filters: I think we need some advice from Ryan here. I don't
> understand what the user interface to filters is supposed to be. How are
> documents supposed to be designated for SSI processing, for example?
Currently, there are two ways to designate a page for filters. The first
is AddFilter. This is a simple directive that just takes a list of
filters. SSI's would be enabled for filters by adding the following:
<Files ~ \.shtml$>
AddFilter INCLUDES
</Files>
The second is SetFilter. This takes a mime-type and a list of
filters. So it would look like:
SetFilter test/html INCLUDES
Hope that helps, if not, let me know what else you need.
> 3. Website: I believe it is time to place the 2.0 docs on the website
> in a similar manner to the 1.3 docs. I don't have the karma to do this
> myself.
Do me a favor, send me a patch, and I'll get this done. All I really
need, is the patch for the actual site. I'll take care of checking out
the actual docs.
I'll try to look at the STATUS file today, but I am focused on a few known
bugs that I want to get rid of ASAP, so it may take me a little while.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------