cvs commit: apache-devsite mailing-lists.html

[brian]

brian   00/02/21 12:13:07

  Modified:.mailing-lists.html
  Log:
  Update mailing list info.
  
  Revision  ChangesPath
  1.6   +16 -26apache-devsite/mailing-lists.html
  
  Index: mailing-lists.html
  ===
  RCS file: /home/cvs/apache-devsite/mailing-lists.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- mailing-lists.html1998/09/02 16:09:42 1.5
  +++ mailing-lists.html2000/02/21 20:13:07 1.6
  @@ -18,27 +18,17 @@
   
   
 
  -  The Apache Project makes very heavy use of mailing lists.
  -  All of these are Majordomo lists, which means that if you want to
  -  subscribe, just send a mail message to
  -  [EMAIL PROTECTED]>
  -  with the following in the message body (not the
  -  subject!).  (The "End" keeps
  -  Majordomo from trying to treat any signature text as commands.)
  -  
  -  
  -  
  -   subscribe list-name
  -
  -end
  -   
  -  
  -  
  +  The Apache Project makes very heavy use of mailing lists.  All of
  +  these are http://www.ezmlm.org/";>ezmlm lists, which
  +  means that if you want to subscribe to list@apache.org
  +  then you want to email list[EMAIL PROTECTED],
  +  for any given list.  If you need help with the various ezmlm commands
  +  for a given list, email list[EMAIL PROTECTED].
  +  Details given below.
  +
 
  mailto:[EMAIL 
PROTECTED]&body=subscribe%20apache-announce%0Dend"
  + HREF="mailto:[EMAIL PROTECTED]"
  >apache-announce
   
   Every time there is a significant announcement to be made about any
  @@ -62,7 +52,7 @@
   
  
  mailto:[EMAIL 
PROTECTED]&body=subscribe%20apache-bugdb%0Dend"
  + HREF="mailto:[EMAIL PROTECTED]"
  >apache-bugdb
   
   This is the mailing list to which all activity in the problem report
  @@ -122,7 +112,7 @@
   
  
  mailto:[EMAIL 
PROTECTED]&body=subscribe%20apache-cvs%0Dend"
  + HREF="mailto:[EMAIL PROTECTED]"
  >apache-cvs
   
   This list is used to notify developers of changes to the master CVS
  @@ -131,7 +121,7 @@
   
  
   
  -   mailto:[EMAIL PROTECTED]&body=subscribe%20apache-docs%0Dend">
  +   mailto:apache-docs-subscribe";
apache-docs

See the
  @@ -139,7 +129,7 @@
>related projects page for more info.

   
  -   mailto:[EMAIL 
PROTECTED]&body=subscribe%20current-testers%0Dend">
  +   mailto:[EMAIL PROTECTED]"
current-testers

This mailing list is for folks who want to test out development
  @@ -150,7 +140,7 @@
in released versions to the bugdb however.

   
  -   mailto:[EMAIL PROTECTED]&body=subscribe%20gui-dev%0Dend">
  +   mailto:[EMAIL PROTECTED]"
gui-dev

See the
  @@ -158,7 +148,7 @@
>related projects page for more info.

   
  -   mailto:[EMAIL PROTECTED]&body=subscribe%20new-httpd%0Dend">
  +   mailto:[EMAIL PROTECTED]"
new-httpd

This list is the primary developer mailing list.  It can be very
  @@ -170,7 +160,7 @@
to the USENET newsgroup "comp.infosystems.www.servers.unix".

   
  -   mailto:[EMAIL 
PROTECTED]&body=subscribe%20stable-testers%0Dend">
  +   mailto:[EMAIL PROTECTED]"
stable-testers

This mailing list is for folks who want to test out development
  
  
  

cvs commit: apache-2.0/src/lib/apr/file_io/unix pipe.c

[rbb]

rbb 00/02/21 10:29:31

  Modified:src/lib/apr/file_io/unix pipe.c
  Log:
  Stupid bug in pipe logic
  
  Revision  ChangesPath
  1.11  +1 -1  apache-2.0/src/lib/apr/file_io/unix/pipe.c
  
  Index: pipe.c
  ===
  RCS file: /home/cvs/apache-2.0/src/lib/apr/file_io/unix/pipe.c,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- pipe.c2000/01/06 14:43:09 1.10
  +++ pipe.c2000/02/21 18:29:31 1.11
  @@ -122,7 +122,7 @@
   (*out)->cntxt = cont;
   (*out)->filedes = filedes[1];
   (*out)->buffered = 0;
  -(*in)->pipe = 1;
  +(*out)->pipe = 1;
   (*out)->fname = ap_pstrdup(cont, "PIPE");
   (*out)->timeout = -1;
   
  
  
  

cvs commit: apache-2.0/src/modules/standard mod_rewrite.c

[stoddard]

stoddard00/02/21 08:41:42

  Modified:src/include ap_iol.h
   src/lib/apr aprlib.def
   src/lib/apr/file_io/beos readwrite.c
   src/lib/apr/file_io/os2 fileio.h readwrite.c
   src/lib/apr/file_io/unix fileio.h readwrite.c
   src/lib/apr/file_io/win32 fileio.h readwrite.c
   src/lib/apr/include apr_file_io.h
   src/main buff.c iol_file.c
   src/modules/standard mod_rewrite.c
  Log:
  Make file I/O and network I/O writev/sendv APIs consistent.
  Eliminate use of ap_iovec_t and use Posix struct iovec. I never
  did hear a case (much less a strong case) supporting the need
  for ap_iovec_t, so out it goes.
  
  Revision  ChangesPath
  1.11  +1 -1  apache-2.0/src/include/ap_iol.h
  
  Index: ap_iol.h
  ===
  RCS file: /home/cvs/apache-2.0/src/include/ap_iol.h,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- ap_iol.h  2000/02/18 18:05:15 1.10
  +++ ap_iol.h  2000/02/21 16:41:38 1.11
  @@ -106,7 +106,7 @@
   ap_status_t (*close)(ap_iol *fd);
   ap_status_t (*write)(ap_iol *fd, const char *buf, ap_size_t len,
ap_ssize_t *nbytes);
  -ap_status_t (*writev)(ap_iol *fd, const ap_iovec_t *vec, int nvec,
  +ap_status_t (*writev)(ap_iol *fd, const struct iovec *vec, int nvec,
 ap_ssize_t *nbytes);
   ap_status_t (*read)(ap_iol *fd, char *buf, ap_size_t len,
   ap_ssize_t *nbytes);
  
  
  
  1.11  +1 -1  apache-2.0/src/lib/apr/aprlib.def
  
  Index: aprlib.def
  ===
  RCS file: /home/cvs/apache-2.0/src/lib/apr/aprlib.def,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- aprlib.def2000/02/18 18:05:16 1.10
  +++ aprlib.def2000/02/21 16:41:39 1.11
  @@ -20,7 +20,7 @@
   ;ap_get_filesize   @12
   ;ap_get_fileatime   @13
   ;ap_get_filectime   @14
  - ap_make_iov   @15
  +;ap_make_iov   @15
ap_dupfile   @16
ap_getfileinfo   @17
ap_open   @18
  
  
  
  1.7   +3 -15 apache-2.0/src/lib/apr/file_io/beos/readwrite.c
  
  Index: readwrite.c
  ===
  RCS file: /home/cvs/apache-2.0/src/lib/apr/file_io/beos/readwrite.c,v
  retrieving revision 1.6
  retrieving revision 1.7
  diff -u -r1.6 -r1.7
  --- readwrite.c   2000/02/05 12:05:06 1.6
  +++ readwrite.c   2000/02/21 16:41:39 1.7
  @@ -127,7 +127,7 @@
   }
   
   /* ***APRDOC
  - * ap_status_t ap_writev(ap_file_t *, ap_iovec_t *, ap_ssize_t *)
  + * ap_status_t ap_writev(ap_file_t *, iovec *, ap_ssize_t *)
*Write data from ap_iovec array to the specified file.
* arg 1) The file descriptor to write to.
* arg 2) The array from which to get the data to write to the file.
  @@ -138,22 +138,10 @@
*written on function exit. 
*/
   #ifdef HAVE_WRITEV
  -
  -ap_status_t ap_make_iov(struct iovec_t **new, struct iovec *iova, 
ap_context_t *cntxt)
  +ap_status_t ap_writev(struct file_t *thefile, const struct iovec *vec, 
ap_ssize_t *iocnt)
   {
  -(*new) = ap_palloc(cntxt, sizeof(struct iovec_t));
  -if ((*new) == NULL) {
  -return APR_ENOMEM;
  -}
  -(*new)->cntxt = cntxt;
  -(*new)->theiov = iova;
  -return APR_SUCCESS;
  -}
  -
  -ap_status_t ap_writev(struct file_t *thefile, const struct iovec_t *vec, 
ap_ssize_t *iocnt)
  -{
   int bytes;
  -if ((bytes = writev(thefile->filedes, vec->theiov, *iocnt)) < 0) {
  +if ((bytes = writev(thefile->filedes, vec, *iocnt)) < 0) {
   *iocnt = bytes;
   return errno;
   }
  
  
  
  1.8   +0 -5  apache-2.0/src/lib/apr/file_io/os2/fileio.h
  
  Index: fileio.h
  ===
  RCS file: /home/cvs/apache-2.0/src/lib/apr/file_io/os2/fileio.h,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- fileio.h  2000/01/10 15:35:45 1.7
  +++ fileio.h  2000/02/21 16:41:39 1.8
  @@ -91,11 +91,6 @@
   int validentry;
   };
   
  -struct iovec_t {
  -ap_context_t *cntxt;
  -struct iovec *theiov;
  -};
  -
   ap_status_t file_cleanup(void *);
   ap_status_t ap_os2_time_to_ap_time(ap_time_t *result, FDATE os2date, FTIME 
os2time);
   int os2errno( ULONG oserror );
  
  
  
  1.12  +2 -15 apache-2.0/src/lib/apr/file_io/os2/readwrite.c
  
  Index: readwrite.c
  ===
  RCS file: /home/cvs/apache-2.0/src/lib/apr/file_io/os2/readwrite.c,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -r1.11 -r1.12
  --- readwrite.c   2000/01/10 15:35:45 1.11
  +

cvs commit: apache-1.3/htdocs/manual/mod mod_rewrite.html

[rse]

rse 00/02/20 23:35:36

  Modified:htdocs/manual/mod mod_rewrite.html
  Log:
  Documentation fixes do not harm anyone, so I feel free to commit this
  English cleanup to the mod_rewrite documentation although we're in code
  freeze state. But we should now really kick out the 1.3.12 baby. We're
  already behind the proposed dates...
  
  Submitted by: G.W. Haywood <[EMAIL PROTECTED]>
  Reviewed by: Ralf S. Engelschall
  
  Revision  ChangesPath
  1.49  +132 -133  apache-1.3/htdocs/manual/mod/mod_rewrite.html
  
  Index: mod_rewrite.html
  ===
  RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/mod_rewrite.html,v
  retrieving revision 1.48
  retrieving revision 1.49
  diff -u -r1.48 -r1.49
  --- mod_rewrite.html  2000/02/05 11:44:06 1.48
  +++ mod_rewrite.html  2000/02/21 07:35:35 1.49
  @@ -81,13 +81,13 @@
   
   This module operates on the full URLs (including the path-info part) both in
   per-server context (httpd.conf) and per-directory context
  -(.htaccess) and even can generate query-string parts on result.
  +(.htaccess) and can even generate query-string parts on result.
   The rewritten result can lead to internal sub-processing, external request
   redirection or even to an internal proxy throughput.
   
   
   But all this functionality and flexibility has its drawback: complexity. So
  -don't expect to understand this module in its whole in just one day.
  +don't expect to understand this entire module in just one day.
   
   
   This module was invented and originally written in April 1996
  @@ -152,46 +152,46 @@
   First you have to understand that when Apache processes a HTTP request it 
does
   this in phases. A hook for each of these phases is provided by the Apache 
API.
   Mod_rewrite uses two of these hooks: the URL-to-filename translation hook
  -which is used after the HTTP request was read and before any authorization
  +which is used after the HTTP request has been read but before any 
authorization
   starts and the Fixup hook which is triggered after the authorization phases
  -and after the per-directory config files (.htaccess) where read,
  -but before the content handler is activated.
  +and after the per-directory config files (.htaccess) have been 
  +read, but before the content handler is activated.
   
   
   So, after a request comes in and Apache has determined the corresponding
  -server (or virtual server) the rewriting engine start processing of all
  +server (or virtual server) the rewriting engine starts processing of all
   mod_rewrite directives from the per-server configuration in the
   URL-to-filename phase. A few steps later when the final data directories are
   found, the per-directory configuration directives of mod_rewrite are 
triggered
  -in the Fixup phase. In both situations mod_rewrite either rewrites URLs to 
new
  +in the Fixup phase. In both situations mod_rewrite rewrites URLs either to 
new
   URLs or to filenames, although there is no obvious distinction between them.
  -This is a usage of the API which was not intended this way when the API
  +This is a usage of the API which was not intended to be this way when the API
   was designed, but as of Apache 1.x this is the only way mod_rewrite can
   operate. To make this point more clear remember the following two points:
   
   
  -The API currently provides only a URL-to-filename hook. Although
  -mod_rewrite rewrites URLs to URLs, URLs to filenames and even
  -filenames to filenames. In Apache 2.0 the two missing hooks 
  -will be added to make the processing more clear. But this
  -point has no drawbacks for the user, it is just a fact which
  -should be remembered: Apache does more in the URL-to-filename hook
  -then the API intends for it.
  +Although mod_rewrite rewrites URLs to URLs, URLs to filenames and
  +even filenames to filenames, the API currently provides only a
  +URL-to-filename hook.  In Apache 2.0 the two missing hooks will be
  +added to make the processing more clear. But this point has no
  +drawbacks for the user, it is just a fact which should be
  +remembered: Apache does more in the URL-to-filename hook than the
  +API intends for it.
   
   Unbelievably mod_rewrite provides URL manipulations in per-directory
  -context, i.e., within .htaccess files, although
  -these are
  -reached a very long time after the URLs were translated to filenames 
(this
  -has to be this way, because .htaccess files stay in the
  -filesystem, so processing has already been reached this stage of
  -processing). In other words: According to the API phases at this time it
  -is too late for any URL manipulations.  To overcome this chicken and egg
  -problem mod_rewrite uses a trick: When you manipulate a URL/filename in
  -per-directory context mod_rewrite first rewrites the filename back to its
  -corresponding URL (

cvs commit: apache-1.3/conf httpd.conf-dist

[rse]

rse 00/02/20 23:30:46

  Modified:conf httpd.conf-dist
  Log:
  Clarify that MultiViews is required for the automatic
  extension checks.
  
  Submitted by: Ian Kallen <[EMAIL PROTECTED]>
  Reviewed by: Ralf S. Engelschall
  
  Revision  ChangesPath
  1.55  +4 -3  apache-1.3/conf/httpd.conf-dist
  
  Index: httpd.conf-dist
  ===
  RCS file: /home/cvs/apache-1.3/conf/httpd.conf-dist,v
  retrieving revision 1.54
  retrieving revision 1.55
  diff -u -r1.54 -r1.55
  --- httpd.conf-dist   2000/01/30 16:18:34 1.54
  +++ httpd.conf-dist   2000/02/21 07:30:46 1.55
  @@ -615,9 +615,10 @@
   # HeaderName is the name of a file which should be prepended to
   # directory indexes. 
   #
  -# The server will first look for name.html and include it if found.
  -# If name.html doesn't exist, the server will then look for name.txt
  -# and include it as plaintext if found.
  +# If MultiViews are amongst the Options in effect, the server will
  +# first look for name.html and include it if found.  If name.html
  +# doesn't exist, the server will then look for name.txt and include
  +# it as plaintext if found.
   #
   ReadmeName README
   HeaderName HEADER