cvs commit: apache-1.3/src CHANGES
coar98/08/06 16:32:03
Modified:htdocs/manual/mod mod_speling.html
src/modules/standard mod_speling.c
src CHANGES
Log:
Allow CheckSpelling to be used anywhere, not just at the server
level.
Revision ChangesPath
1.9 +27 -12apache-1.3/htdocs/manual/mod/mod_speling.html
Index: mod_speling.html
===
RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_speling.html,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- mod_speling.html 1998/05/20 14:12:59 1.8
+++ mod_speling.html 1998/08/06 23:31:55 1.9
@@ -70,8 +70,14 @@
A
HREF=directive-dict.html#Context
REL=Help
- STRONGContext:/STRONG/A server config, virtual hostBR
+ STRONGContext:/STRONG/A server config, virtual host,
+ directory, .htaccessBR
A
+ HREF=directive-dict.html#Override
+ REL=Help
+ STRONGOverride:/STRONG/A Options
+ BR
+ A
HREF=directive-dict.html#Status
REL=Help
STRONGStatus:/STRONG/A BaseBR
@@ -85,20 +91,29 @@
STRONGCompatibility:/STRONG/A CheckSpelling was available as a
separately
available module for Apache 1.1, but was limited to miscapitalizations.
- As of Apache 1.3, it is part of the Apache distribution!-- or:
- available as a separate module--.P
-
+ As of Apache 1.3, it is part of the Apache distribution. Prior to
+ Apache 1.3.2, the SAMPCheckSpelling/SAMP directive was only available
+ in the server and virtual host contexts.
+ P
This directive enables or disables the spelling module. When enabled,
keep in mind that
+ /P
UL
- LIthe directory scan which is necessary for the spelling
- correction will have an impact on the server's performance
- when many spelling corrections have to be performed at the same time.
- LIthe document trees should not contain sensitive files which could
- be matched inadvertently, by a spelling correction.
- LIthe module is unable to correct misspelled user names
- (as in CODEhttp://my.host/~apahce//CODE), just file names or
- directory names.
+ LIthe directory scan which is necessary for the spelling
+ correction will have an impact on the server's performance
+ when many spelling corrections have to be performed at the same time.
+ /LI
+ LIthe document trees should not contain sensitive files which could
+ be matched inadvertently by a spelling correction.
+ /LI
+ LIthe module is unable to correct misspelled user names
+ (as in CODEhttp://my.host/~apahce//CODE), just file names or
+ directory names.
+ /LI
+ LIspelling corrections apply strictly to existing files, so a request
for
+ the SAMPlt;Location /statusgt;/SAMP may get incorrectly treated
+ as the negotiated file SAMP/stats.html/SAMP.
+ /LI
/UL
!--#include virtual=footer.html --
1.24 +47 -14apache-1.3/src/modules/standard/mod_speling.c
Index: mod_speling.c
===
RCS file: /export/home/cvs/apache-1.3/src/modules/standard/mod_speling.c,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- mod_speling.c 1998/08/06 17:31:11 1.23
+++ mod_speling.c 1998/08/06 23:31:59 1.24
@@ -85,31 +85,64 @@
MODULE_VAR_EXPORT module speling_module;
+typedef struct {
+int enabled;
+} spconfig;
+
+/*
+ * Create a configuration specific to this module for a server or directory
+ * location, and fill it with the default settings.
+ *
+ * The API says that in the absence of a merge function, the record for the
+ * closest ancestor is used exclusively. That's what we want, so we don't
+ * bother to have such a function.
+ */
+
+static void *mkconfig(pool *p)
+{
+spconfig *cfg = ap_pcalloc(p, sizeof(spconfig));
+
+cfg-enabled = 0;
+return cfg;
+}
+
/*
- * We use the unconventional mod_userdir approach here. And heck,
- * here it's just one int!
+ * Respond to a callback to create configuration record for a server or
+ * vhost environment.
*/
+static void *create_mconfig_for_server(pool *p, server_rec *s)
+{
+return mkconfig(p);
+}
-static void *create_speling_config(pool *dummy, server_rec *s)
+/*
+ * Respond to a callback to create a config record for a specific directory.
+ */
+static void *create_mconfig_for_directory(pool *p, char *dir)
{
-return (void *) 0;
+return mkconfig(p);
}
-static const char *set_speling(cmd_parms *cmd, void *dummy, int arg)
+/*
+ * Handler for the CheckSpelling directive, which is FLAG.
+ */
+static const char *set_speling(cmd_parms *cmd, void *mconfig, int arg)
{
-void *server_conf =
cvs commit: apache-devsite bugdb-policies.html
coar98/08/07 02:16:51
Modified:.bugdb-policies.html
Log:
Downsize the typeface inside the tables for better readability and
printability.
Reviewed by: Ralf Engelschall
Revision ChangesPath
1.2 +159 -143 apache-devsite/bugdb-policies.html
Index: bugdb-policies.html
===
RCS file: /export/home/cvs/apache-devsite/bugdb-policies.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- bugdb-policies.html 1998/08/03 14:48:27 1.1
+++ bugdb-policies.html 1998/08/07 09:16:49 1.2
@@ -4,6 +4,11 @@
HEAD
TITLEApache Bug Database Policies for Developers
/TITLE
+ STYLE TYPE=text/css
+ !--
+ TD { font-size: smaller }
+ --
+ /STYLE
/HEAD
!-- Background white, links blue (unvisited), navy (visited), red (active)
--
BODY
@@ -151,148 +156,159 @@
state should be for a PR you're handling, consult the table for some
guidelines.
/P
- TABLE BORDER=1
- TR VALIGN=BOTTOM ALIGN=CENTER
-TD/TD
-THopen/TH
-THanalyzed/TH
-THfeedback/TH
-THsuspended/TH
-THclosed/TH
- /TR
- TR VALIGN=TOP
-TH VALIGN=CENTERopen/TH
-TD!-- open-open --
-/TD
-TD!-- open-analyzed --
- Either the submitter or a responding developer has determined what the
- problem cause is.
-/TD
-TD!-- open-feedback --
- A question has been posed to the submitter, such as asking for more
- detail or requesting an experiment.
-/TD
-TD!-- open-suspended --
- The PR describes a request for a change or functionality that is
- reasonable or interesting, but isn't appropriate to the current
- version under development, or to the current plans or work effort
- available.
-/TD
-TD!-- open-closed --
- The PR deals with a non-issue, one that has already been solved, or is
- already being tracked. Or almost any case in which further attention
- is inappropriate.
-/TD
- /TR
- TR VALIGN=TOP
-TH VALIGN=CENTERanalyzed/TH
-TD!-- analyzed-open --
- It turns out that the analysis was incorrect and the cause really isn't
- known after all.
-/TD
-TD!-- analyzed-analyzed --
-/TD
-TD!-- analyzed-feedback --
- The submitter is being asked for more information or experimentation.
-/TD
-TD!-- analyzed-suspended --
- The issue described by the PR should be deferred until some later
version.
-/TD
-TD!-- analyzed-closed --
- The decision has been made to STRONGnot/STRONG address the PR,
- possibly because the behaviour is not considered a bug. This usually
- follows discussion amongst the developers.
-/TD
- /TR
- TR VALIGN=TOP
-TH VALIGN=CENTERfeedback/TH
-TD!-- feedback-open --
- The requested information has been supplied by the submitter, but
- doesn't really explain the behaviour. (It may be more appropriate to
- move the PR to analyzed instead.)
-/TD
-TD!-- feedback-analyzed --
- The response from the submitter has provided the necessary information
- to determine the cause, if not the solution, of the issue.
-/TD
-TD!-- feedback-feedback --
-/TD
-TD!-- feedback-suspended --
- Additional information from the submitter allows the determination to
- be made that the issue should be addressed in some future version.
-/TD
-TD!-- feedback-closed --
- MENU
- LIAdditional information supplied by the submitter has explained the
- cause, and the solution is provided in the closure text.
- /LI
- LIThe PR has 'A HREF=#datestimed out/A' due to lack of response
- from the submitter.
- /LI
- /MENU
-/TD
- /TR
- TR VALIGN=TOP
-TH VALIGN=CENTERsuspended/TH
-TD!-- suspended-open --
- MENU
- LIThe time has come for the issue described by the PR to be
considered
- for inclusion in the project.
- /LI
- LIThe PR describes a genuine bug rather than a change or enhancement.
- It may be more appropriate to move the PR to analyzed instead.
- /LI
- /MENU
-/TD
-TD!-- suspended-analyzed --
- MENU
- LIThe time has come for the issue described by the PR to be
considered
- for inclusion in the project.
- /LI
- LIThe issue described by the PR is a genuine bug or problem, and the
- circumstances are tolerably well understood.
- /LI
- /MENU
-/TD
-TD!-- suspended-feedback --
- The PR's issue wasn't clearly understood, and it really is a bug
- report. More information from the submitter has been requested.
- (This typically follows A
cvs commit: apache-1.3/src/main http_main.c
dgaudet 98/08/07 08:35:54
Modified:src CHANGES
src/main http_main.c
Log:
fix os/2 mutex problem
Submitted by: Brian Havard
Revision ChangesPath
1.1010+2 -0 apache-1.3/src/CHANGES
Index: CHANGES
===
RCS file: /export/home/cvs/apache-1.3/src/CHANGES,v
retrieving revision 1.1009
retrieving revision 1.1010
diff -u -r1.1009 -r1.1010
--- CHANGES 1998/08/06 23:32:01 1.1009
+++ CHANGES 1998/08/07 15:35:45 1.1010
@@ -1,5 +1,7 @@
Changes with Apache 1.3.2
+ *) Fix a problem with the new OS/2 mutexes. [Brian Havard]
+
*) Enhance mod_spelling so that CheckSpelling can be used in
Directory containers and .htaccess files. [Ken Coar]
1.380 +1 -0 apache-1.3/src/main/http_main.c
Index: http_main.c
===
RCS file: /export/home/cvs/apache-1.3/src/main/http_main.c,v
retrieving revision 1.379
retrieving revision 1.380
diff -u -r1.379 -r1.380
--- http_main.c 1998/08/06 17:30:29 1.379
+++ http_main.c 1998/08/07 15:35:49 1.380
@@ -845,6 +845,7 @@
static void accept_mutex_cleanup(void *foo)
{
+DosReleaseMutexSem(lock_sem);
DosCloseMutexSem(lock_sem);
}
