Re: todos for 2.3.1-alpha
On Wed, Dec 30, 2009 at 2:20 AM, Niklas Edmundsson ni...@acc.umu.se wrote: On Tue, 29 Dec 2009, William A. Rowe Jr. wrote: How about increasing worker_score::request? This was originally proposed in Oct 2007. http://mail-archives.apache.org/mod_mbox/httpd-dev/200710.mbox/%3cpine.gso.4.64.0710201228590.22...@kleopatra.acc.umu.se%3e I know this is an old topic, but I just ran into this again. Any chance we could see something like this make it in the 2.3.X branch? I did not see a reply on this. Wouldn't it make sense to pack multi-ascii fields in a single text block? Folks rarely use the entire 64 characters of the remote machine or vhost name. It probably would, although I suspect that it would break quite a few modules, or? If we want to do that now's the time though. I think most modules worked around the scoreboard limitations, so likely would not see any impact. However, I still think that increasing the thing from 64 to 256 bytes would solve most peoples problems without taxing memory too much. If noone has the time to do the elegant fix, I would opt for at least doing the easy kludge for now... Right and most modules that would make use of this seem to have gone the route of doing their own accounting by hooking into log transaction hook and storing that data out of bound. None of mod_telemetry, mod_bw, etc. seem to share this data and almost all duplicate the scoreboard data. It is understandable that they all need a place to store their specific accounting details, but you'd hope they would be able to reuse and key off of the scoreboard for things in common. Instrumenting and monitoring solutions also could use access to this data. Ideally we would provide r-notes type functionality for modules to use in respect of the scoreboard while storing the same size fields of request_rec that are commonly used by all these types of modules. -- Sander
Re: todos for 2.3.1-alpha
On Fri, Dec 12, 2008 at 4:45 PM, Takashi Sato taka...@lans-tv.com wrote: On Fri, 12 Dec 2008 12:27:11 -0800 Paul Querna c...@force-elite.com wrote: Anything else anyone thinks would be good to get in? How about increasing worker_score::request? This was originally proposed in Oct 2007. http://mail-archives.apache.org/mod_mbox/httpd-dev/200710.mbox/%3cpine.gso.4.64.0710201228590.22...@kleopatra.acc.umu.se%3e Hi, I know this is an old topic, but I just ran into this again. Any chance we could see something like this make it in the 2.3.X branch? I did not see a reply on this. -- Sander van Zoest
Re: DO NOT REPLY [Bug 9181] - Unable to set headers on non-2XX responses.
On Fri, Oct 04, 2002 at 01:35:06PM -0400, [EMAIL PROTECTED] wrote: Please do not close bug reports without entering some kind of information about why it is being closed. It is CLOSED, because I agree with the fact that it is RESOLVED. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: cvs commit: apache-1.3/src/modules/standard mod_headers.c
On Thu, Sep 26, 2002 at 10:22:11AM -0700, Aaron Bannert wrote: On Thu, Sep 26, 2002 at 07:51:42AM -0500, William A. Rowe, Jr. wrote: Hmmm. If it was written by Michael, I'd think; Was it? Yes. Michael Radwin wrote the code. I wanted to make sure he got credit for that. After talking to Michael about submitting it. I just double checked that it would work on HEAD and submitted it, since he didn't have the time for that. Sorry for the confusion. -- Sander van Zoest +1 (619) 881-3000 Yahoo!, Inc. [EMAIL PROTECTED] http://www.yahoo.com/ http://sander.vanzoest.com/
Re: [PATCH] Alerting when fnctl is going bad
On Wed, 25 Sep 2002, Justin Erenkrantz wrote: On Thu, Sep 26, 2002 at 02:11:59AM +0200, Dirk-Willem van Gulik wrote: - Makes the wait loop no longer endless - but causes it to bail out (and emit some warnings ahead of time) after a couple of thousand consequituve EINTRs. Placing a 'magic number' on how many EINTRs is 'failure' doesn't seem right. -- justin Although, things like these have been done many times in the past. Especially in BSD. As long as the number is high enough to where there doesn't seem to be an obvious reason to go above that, then I do not see why not. As for example, the limit of 7 dereferences on a symlink to prevent symlink infinite loops. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
[PATCH] 1.3.X Re: Include conf.d/*.conf
On Wed, Sep 11, 2002 at 06:56:12AM +0100, Joe Orton wrote:
On Tue, Sep 10, 2002 at 09:21:17PM -0700, Justin Erenkrantz wrote:
On Tue, Sep 10, 2002 at 04:04:31PM -0700, Ian Holsman wrote:
does anyone recall if there was a good reason not to include this patch
in the main distribution ?
What patch is this? -- justin
I hadn't had time to submit the revised patch yet: here it is.
Please find a patch for 1.3 attached.
This patch does *not* remove the noise.
Cheers,
--
Sander van Zoest +1 (619) 881-3000
Yahoo!, Inc. [EMAIL PROTECTED]
http://www.yahoo.com/ http://sander.vanzoest.com/
Index: http_config.c
===
RCS file: /work/cvs/root/asf/httpd/apache-1.3/src/main/http_config.c,v
retrieving revision 1.163
diff -u -p -r1.163 http_config.c
--- http_config.c 13 Mar 2002 21:05:30 - 1.163
+++ http_config.c 12 Sep 2002 19:36:21 -
@@ -81,6 +81,7 @@
#include http_conf_globals.h /* Sigh... */
#include http_vhost.h
#include explain.h
+#include fnmatch.h
DEF_Explain
@@ -1211,7 +1212,7 @@ CORE_EXPORT(void) ap_process_resource_co
const char *errmsg;
cmd_parms parms;
struct stat finfo;
-
+int ispatt;
fname = ap_server_root_relative(p, fname);
if (!(strcmp(fname, ap_server_root_relative(p, RESOURCE_CONFIG_FILE))) ||
@@ -1233,12 +1234,38 @@ CORE_EXPORT(void) ap_process_resource_co
* horrible loops). If so, let's recurse and toss it back into
* the function.
*/
-if (ap_is_rdirectory(fname)) {
+ispatt = ap_is_fnmatch(fname);
+if (ispatt || ap_is_rdirectory(fname)) {
DIR *dirp;
struct DIR_TYPE *dir_entry;
int current;
array_header *candidates = NULL;
fnames *fnew;
+ char *path = ap_pstrdup(p,fname);
+ char *pattern = NULL;
+
+if(ispatt) {
+ pattern = strrchr(path, '/');
+*pattern++ = '\0';
+if (ap_is_fnmatch(path)) {
+fprintf(stderr, %s: wildcard patterns not allowed in Include
+%s\n, ap_server_argv0, fname);
+exit(1);
+}
+
+if (!ap_is_rdirectory(path)){
+fprintf(stderr, %s: Include directory '%s' not found,
+ap_server_argv0, path);
+exit(1);
+}
+if (!ap_is_fnmatch(pattern)) {
+fprintf(stderr, %s: must include a wildcard pattern
+for Include %s\n, ap_server_argv0, fname);
+exit(1);
+}
+
+}
+
/*
* first course of business is to grok all the directory
@@ -1246,11 +1273,11 @@ CORE_EXPORT(void) ap_process_resource_co
* for this.
*/
fprintf(stderr, Processing config directory: %s\n, fname);
- dirp = ap_popendir(p, fname);
+ dirp = ap_popendir(p, path);
if (dirp == NULL) {
perror(fopen);
fprintf(stderr, %s: could not open config directory %s\n,
- ap_server_argv0, fname);
+ ap_server_argv0, path);
#ifdef NETWARE
clean_parent_exit(1);
#else
@@ -1261,9 +1288,11 @@ CORE_EXPORT(void) ap_process_resource_co
while ((dir_entry = readdir(dirp)) != NULL) {
/* strip out '.' and '..' */
if (strcmp(dir_entry-d_name, .)
- strcmp(dir_entry-d_name, ..)) {
+ strcmp(dir_entry-d_name, ..)
+(!ispatt ||
+ !ap_fnmatch(pattern,dir_entry-d_name, FNM_PERIOD)) ) {
fnew = (fnames *) ap_push_array(candidates);
- fnew-fname = ap_make_full_path(p, fname, dir_entry-d_name);
+ fnew-fname = ap_make_full_path(p, path, dir_entry-d_name);
}
}
ap_pclosedir(p, dirp);
Re: CVS, SSH and Windows
On Tue, Sep 10, 2002 at 01:18:10PM -0700, Sander Temme wrote: When you figure it out, please update the developer docs (on httpd.apache.org/dev/) with the info. and howtos, and have got nowhere - SSH insists on asking for a password on every connection attempt, and won't cooperate. You need to convince CVS to use public key authentication. Are you using the cygwin ssh? In that case, generate a public/private key pair using ssh-keygen. The private key goes (probably already is) in the ~/.ssh directory; copy the public key over to the ssh server and rename/append to ~/.ssh/authorized_keys. If you have generated ssh2 compatible keys, that file should be named authorized_keys2. Proof of the pudding: if you can ssh in without specifying password from the shell, WinCVS should be able to do it, too. From the shell, debug using ssh -v. You may also want to look at using pageant (PuTTY ssh-agent), which will authenticate pass-phrases upon startup, to allow passphraseless login. http://www.chiark.greenend.org.uk/~sgtatham/putty/ On MacOS X.2 use http://www.opendarwin.org/~kevin/SSHAgentStartup.tar.gz -- Sander van Zoest +1 (619) 881-3000 Yahoo!, Inc. [EMAIL PROTECTED] http://www.yahoo.com/ http://sander.vanzoest.com/
Re: Jaguar autoconf bug
On Tue, Sep 10, 2002 at 04:09:39PM -0400, Jim Jagielski wrote: From http://www.osxgnu.org/#jagbugs August, 31 2002: Major Bug found in the GNU Autoconf implementation on 10.2 Jaguar! In the file /usr/share/autoconf/autoconf.m4f line 7294 should read: exit (setpgrp (0,0) == -1);])], not exit (setpgrp (1,1) == -1);])], As a result any program using GNU configure may not compile (just about all of them). You may wish to edit this file to reflect the above changes -- There is a new August 2002 Dev Tools 10.2 Update available from ADC. -- http://developer.apple.com/ August 2002 Dev Tools 10.2 Update The August 2002 Mac OS X Developer Tools Update addresses issues with the July 2002 Mac OS X Developer Tools originally released with Mac OS X version 10.2 (Jaguar build 6C115 or later). File Name Date Posted Format File Size August 2002 Dev Tools 10.2 Update 28 Aug 2002 MacBinary 9.9 MB -- http://developer.apple.com/tools/ Note: An August 2002 Developer Tools Update has just been released, which provides an update to the July 2002 Mac OS X Developer Tools. This important patch addresses problems with the development tools (including gcc, gdb, and Interface Builder) that were solved too late to ship with the July 2002 Developer Tools that ship with Mac OS X version 10.2.x. IOKit and kernel developers in particular should install this patch before building release versions of their kexts. [August 29 2002] I am not sure if this addresses this issue, since I do not have my machine with me. But I wouldn't be too surprised if it did. -- Sander van Zoest +1 (619) 881-3000 Yahoo!, Inc. [EMAIL PROTECTED] http://www.yahoo.com/ http://sander.vanzoest.com/
Re: El-Kabong -- HTML Parser
On Thu, 29 Aug 2002, Jon Travis wrote: On Thu, Aug 29, 2002 at 11:29:24AM -0700, Aaron Bannert wrote: On Thu, Aug 29, 2002 at 02:24:28PM -0400, Ryan Bloom wrote: I will make one exception to that statement. If it lands inside of APR-util, under the XML directory, and it is made to work with the XML parser, I can accept that landing spot. As it fits in closer with our goals (I think). Jim, I can't decide if this is what you meant or not. I'm +1 on integrating it into our XML stuff. I consider it to be equivalent to apr-util, so either we put it inside apr-util, or we create a new APR subproject or sub-library for it. I'm not keen on integrating it into the APR XML layer for a few reasons: 1 - APR's XML is not SAX-stylee. El-Kabong is. That isn't to say that E-K couldn't get a full object model interface, but it doesn't have it now. Expat is a stream based parsers that is pretty similar to SAX2. It isn't a DOM xml parser. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: v1.3.25 (PR#9181)
On Wed, 29 May 2002, Martin Kraemer wrote: On Tue, May 28, 2002 at 09:56:38AM -0700, Sander van Zoest wrote: Can we add in PR#9181? More and more people will run into this issue. -0.5 (it's a feature, and is actively being used by many). Or did you mean add the new directive AcceptPathInfo off? In that case, +1 (but within the time frame, not required for a 1.3.25 release IMO). Ehmm.. I meant the one in the Bugzilla database. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9181 Cheers, -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: v1.3.25 (PR#9181)
On Tue, 28 May 2002, Graham Leggett wrote: There has been much talk of releasing v1.3.25, but no actual release - I am starting to really need the new proxy fixes since v1.3.22 - is there a release planned for the near future? The status says end of May - is it possible to release now? Can we add in PR#9181? More and more people will run into this issue. Cheers, -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: [PATCH] improve config dir processing
On Tue, May 28, 2002 at 04:01:57PM +0100, Joe Orton wrote: On Tue, May 28, 2002 at 07:32:10AM -0700, Justin Erenkrantz wrote: On Tue, May 28, 2002 at 02:04:47PM +0100, Joe Orton wrote: This removes support for Include somedir, by the argument that include dirs will just trip people up unexpectedly, and Include somedir/* is equivalent if they really want that behaviour. (Although the ability to recurse into subdirectories is also removed, I don't think that's particularly useful either) Why do we want to remove the Include somedir feature that has been there for a while? I'm not sold on removing that so quickly without a good rationale. -- justin The rationale goes: the feature is not really usable (you can't use it easily with any editor which creates config files), and has surprising behaviour (it works fine until you change a config file). I'd be surprised if very many people are using it, and they can still get the same effect using Include dir/* (except for the recursion). We use it to add module specific functionality with just dropping in a config file. Then doing a restart we automaticly get the new components added. No need to adjust the actual httpd.conf file. Granted this doesn't work for everything, but works pretty well for most of our cases. -- Sander van Zoest +1 (619) 881-3000 Yahoo!, Inc. [EMAIL PROTECTED] http://www.yahoo.com/ http://sander.vanzoest.com/
Re: libexpat
On Mon, 20 May 2002, Jon Travis wrote: On Mon, May 20, 2002 at 09:54:16PM -0500, William A. Rowe, Jr. wrote: At 09:43 PM 5/20/2002, you wrote: On Mon, 20 May 2002, William A. Rowe, Jr. wrote: Context? httpd links in expat, perl extension links against a different version of expat. both have the same symbol names, and they are not binary compatible. perl extension resolves symbols to the httpd version. kaboom. its been an issue for years with 1.3, you'll find plenty in the modperl archives on it. Can we somehow draw one from the two? Of course that's win32 (or OS X) ... on Unix I can imagine this is hellish, no matter how we try solving it. This same stuff comes up every few months. Python modules had the same issue with PCRE stuff (surprised mod_perl doesn't have that issue). Same issue with libc's regcomp and hsregex. We probably will have the same issue with APR as well. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
[PATCH] 1.3.X mod_headers: New Directive ErrorHeader
It is common practice to set Cookie's to pass along on HTTP
redirects for login authentication.
When implementing P3P http://www.w3.org/P3P/ using
mod_headers.c the Header directive only sets r-headers_out
and does not pass the headers along for non-2XX responses
such as error pages and redirects.
To provide this functionality we added the ErrorHeader
directive which populates r-err_headers_out instead.
Below follows a patch for 1.3.X by Michael Radwin.
I have some code that attempts to add Directive to 2.0.X, but
it seems that output_filters are shortcuted on 3XX responses.
While now by setting the Header directive it also passes the headers
along at for all non-2XX responses except 3XX responses.
Cheers,
--
Sander van Zoest +1 (619) 881-3000
Yahoo!, Inc. [EMAIL PROTECTED]
http://www.yahoo.com/ http://sander.vanzoest.com/
Index: apache-1.3/src/modules/standard/mod_headers.c
===
RCS file: /work/cvs/root/asf/httpd/apache-1.3/src/modules/standard/mod_headers.c,v
retrieving revision 1.27
diff -u -p -r1.27 mod_headers.c
--- apache-1.3/src/modules/standard/mod_headers.c 13 Mar 2002 21:05:33 -
1.27
+++ apache-1.3/src/modules/standard/mod_headers.c 16 May 2002 04:41:08 -
@@ -116,6 +116,7 @@ typedef struct {
hdr_actions action;
char *header;
char *value;
+int do_err;
} header_entry;
/*
@@ -128,6 +129,9 @@ typedef struct {
module MODULE_VAR_EXPORT headers_module;
+static char c_err;
+#define HDR_ERR c_err
+
static void *create_headers_config(pool *p, server_rec *s)
{
headers_conf *a =
@@ -169,6 +173,12 @@ static const char *header_cmd(cmd_parms
new = (header_entry *) ap_push_array(serverconf-headers);
}
+if (cmd-info == HDR_ERR) {
+ new-do_err = 1;
+} else {
+ new-do_err = 0;
+}
+
if (!strcasecmp(action, set))
new-action = hdr_set;
else if (!strcasecmp(action, add))
@@ -200,6 +210,8 @@ static const command_rec headers_cmds[]
{
{Header, header_cmd, NULL, OR_FILEINFO, TAKE23,
an action, header and value},
+{ErrorHeader, header_cmd, HDR_ERR, OR_FILEINFO, TAKE23,
+ an action, header and value},
{NULL}
};
@@ -209,18 +221,19 @@ static void do_headers_fixup(request_rec
for (i = 0; i headers-nelts; ++i) {
header_entry *hdr = ((header_entry *) (headers-elts))[i];
+ table *tbl = (hdr-do_err ? r-err_headers_out : r-headers_out);
switch (hdr-action) {
case hdr_add:
-ap_table_addn(r-headers_out, hdr-header, hdr-value);
+ap_table_addn(tbl, hdr-header, hdr-value);
break;
case hdr_append:
-ap_table_mergen(r-headers_out, hdr-header, hdr-value);
+ap_table_mergen(tbl, hdr-header, hdr-value);
break;
case hdr_set:
-ap_table_setn(r-headers_out, hdr-header, hdr-value);
+ap_table_setn(tbl, hdr-header, hdr-value);
break;
case hdr_unset:
-ap_table_unset(r-headers_out, hdr-header);
+ap_table_unset(tbl, hdr-header);
break;
}
}
@@ -264,5 +277,7 @@ module MODULE_VAR_EXPORT headers_module
NULL, /* child_exit */
NULL/* post read-request */
};
+
+
RE: [PATCH] AddOutputFiltersbyType (revised)
On Tue, 19 Mar 2002, Ryan Bloom wrote: On a note in the original message, adding the same filter twice is okay to do. In fact, it is arguably correct. If I have a filter that changes my c-t to a type that causes me to filter the data again, then I had better re-insert the filter. The biggest problem is going to be infinite loops in this situation, but I am not sure how to protect against that. Protect it like a BSD system would. If you have the same filter more then an arbitrary amount (let's say 7) times on the stack, you probably didn't mean to do that, so make it error out. That is pretty much how BSD 4.4 lite protects symlink loops on the file system. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: Apache-1.3 proxy: X-Cache question
On Thu, 14 Mar 2002, Martin Kraemer wrote: On Thu, Mar 14, 2002 at 12:25:47PM +0100, Kraemer, Martin wrote: X-Cache: MISS from localhost Should the X-Cache line not rather read: X-Cache: MISS from localhost:8080 I just looked at squid's implementation. It doesn't append the port either. But IMHO that's a bug too. In the case of Squid it could be that the request was made via HTCP or ICP rather then HTTP. So the port number might still be useful, but it might be that HTTP is not spoken on this port number. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: putting mod_scoreboard_send in core?
On Wed, 13 Mar 2002, Doug MacEachern wrote: in general, the concept is to serialize the scoreboard in such a way that it can transfered over the network via http and thawed on another machine. i'm sure there's a better way to do this than the mod_scoreboard_send thinger. I have done this in two ways with tools that are not in the httpd core. - have SNMP polls to mod_nsmp(1) and then display it using MRTG, HP OpenView Scotty, or whatever - use mod_status_xml(2) and do periodic GET and use XSLT/SVG to merge the content into a pretty graph/HTML page. I really do not see why this needs to be in the httpd core. 1) the SNMPv3 capable http://www.covalent.net/products/managed/ or http://www.simpleweb.org/software/packages/mod-snmp/ 2) http://www.awe.com/mark/dev/mod_status_xml/ with some contributed changes. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: PROPOSAL: new directive for mod_proxy
On Fri, 8 Mar 2002, Graham Leggett wrote: Aaron Bannert wrote: +1 on adding new directives and not extending Options, especially since this directive only relates to mod_proxy. I don't see why. In the case of mod_autoindex it already uses IndexOptions, maybe creating a ProxyOptions is a better choice here? The standard way of setting what is allowed and what is not allowed in an URL space is via Options. If proxy has its own directive, but everything else uses options, it's confusing and inconsistent. In that vain, you could consider IndexOptions to be inconsistent. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: Torching ap_document_root
On Thu, Mar 07, 2002 at 02:25:56PM -0800, Greg Stein wrote:
server/core.c:661
AP_DECLARE(const char *) ap_document_root(request_rec *r)
If we shouldn't use it, why is it still here?
So the /* don't use this! */ comment should go?
I would say rewrite it to be something like:
Modules shouldn't be worried about the document root. If you need to call
this function, then you should ask yourself why. Modules should be more
concerned with r-uri and r-filename.
There are some cases modules need to have access to the document root
(if not modify it for the duration of the request).
In the case of using a CGI with mod_vhost_alias it would be
nice to be able to have the CGI have access to the virtual document root
via ENV{DOCUMENT_ROOT}. Right now this doesn't seem possible because
mod_vhost_alias does not have access to it and otherwise
ap_add_cgi_vars(r) resets it if we set it via r-subprocess_env in
mod_vhost_alias.
We actually had to hack the core to get this to function appropriately.
Cheers,
--
Sander van Zoest +1 (619) 881-3000
Yahoo!, Inc. [EMAIL PROTECTED]
http://www.yahoo.com/ http://sander.vanzoest.com/
RE: Log file rotation... log sub system
On Sat, 2 Mar 2002, Ryan Bloom wrote: [EMAIL PROTECTED] wrote: Perhaps the logging module should be split up in the same way, with mod_log handling the hooks, and mod_log_disk handling logging direct to disk, mod_log_sql handling direct to database, etc. Wouldn't just making ap_log_error() ap_run_log_error() solve a lot of these problems? ap_log_error_core already runs a hook to allow module to do more with the error log, so this is effectively already done. Do we maybe want to document these? It seems that half the time someone asks a question on how to do something, it can already be done, but there is no real way to know this unless you stare at the code every day. -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: cvs commit: httpd-2.0/server core.c
On Sun, 24 Feb 2002, Brian Pane wrote: [EMAIL PROTECTED] wrote: RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP: + +* With AP_MODE_EXHAUSTIVE in the core, it is finally clear to me + how the Perchild MPM should be re-written. It hasn't worked + correctly since filters were added because it wasn't possible to + get the content that had already been written and the socket at + the same time. This mode lets us do that, so the MPM can be + fixed. -1 on an MPM rewrite until after 2.0 GA is released I would agree with Brian here. We should get 2.0 out and punt on per-child for now. Let's get this baby stable and performant and out to the public. Cheers, -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: Modules.apache.org development mailing list!!!!
On Fri, 22 Feb 2002, Ryan Bloom wrote: While we are at it, Covalent has decided to open archives.covalent.net so that people can hack on that site as well. Once we get a group of people on the mailing list to discuss how we want to do modules.apache.org, we can decide if and how we want to tackle archives.covalent.net, and that can include re-naming it to archives.apache.org, although Covalent would like to keep an alias to archives.covalent.net as well. It used to be at http://archive.covalent.net/ and was also reachable via http://mail-archives.apache.org/ but this got lost in the downtime and office move. We should probably update the IP so mail-archives.apache.org works again. Although most people use MARC now these days anyways. Cheers, -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: modules.apache.org
On Tue, 12 Feb 2002, Ryan Bloom wrote: This has historically been a Covalent hosted and driven project, as a service to the Apache community. Covalent has decided to open that project up to the community to improve. To that end, sometime next week, I will be setting up a machine as a web server and CVS server to be used for modules.apache.org. I might be interested, but under what license will this be set up? I would presume BSD or ASF? One of the first things would probably to provide a hierachy listing, so we all don't have to do empty search queries. Cheers, -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: --with-module annoyingness
On Mon, 4 Feb 2002, Ryan Bloom wrote: Would anybody mind if --with-module created a symbolic link in the modules/foo/ directory to the specified module? Right now, we copy the module to that directory, which means that if you edit the .c file, it gets out of sync with the version in the original directory. If you have the .c file under revision control, that gets annoying quickly. I would keep in mind that the module could reside on a read-only file system and make sure it plays well with --srcdir/--shadow. Cheers, -- Sander van Zoest [EMAIL PROTECTED] San Diego, CA, US http://Sander.vanZoest.com/
Re: [PATCH] Allow DocumentRoot within Location blocks
On Mon, 7 Jan 2002, William A. Rowe, Jr. wrote: From: Ryan Bloom [EMAIL PROTECTED] I would like to discuss the reasoning behind this change. Why are we trying to overload the meaning of DocumentRoot this way? Because it allows the DocumentRoot to be, well, nonexistant. This is very useful in environments where you want an URI space that doesn't necessarily line up with anything on a file system. This would be very useful for things such as mod_perl, XML/XSLT solutions, RTSP/Icecast servers, etc. It allows us to have the following section; Location /nowhere DocumentRoot unset /Location that makes it 100% clear where nowhere goes. It is also possibly easier than alias, since I am not sure if I like the unset keyword. In the mime and handler case we use Add/Remove and we use On and Off already. Maybe using Off is valid here? Then we could probably also use On to enable the DocumentRoot again, where it would enable it to a previously set DocumentRoot higher up in the tree or default to the compiled in default if there was nothing defined elsewhere. works the same as Alias /private /some/private/resource Location /private Options deny,allow Allow from only.me /Location (I assume here you meant Order instead of Options) You could also potentially consider writing this as Directory /some/private/resource Alias /private # Or maybe Uri /private Options deny,allow Allow from only.me /Directory This does not change the notion of having a single DocumentRoot and allows for the same flexibility (if we remove the requirement for a DocumentRoot and allow for DocumentRoot [Off|unset|path] or whatever). Cheers, -- Sander van Zoest [EMAIL PROTECTED] High Geek http://Sander.vanZoest.com/
Re: Logs and logs and logs [oh my!]
On Sun, 30 Dec 2001, William A. Rowe, Jr. wrote:
And if we offer a built-in (or default-config'ed) 'cookie' format,
of %{Cookie}n \%r\ %t, then it's a two bit change to turn a CookieLog
into a CustomLog file cookie command.
I added the %{COOKIE_NAME}C to 2.0 for logging a simple cookie. This
is most likely more useful to most then the CookieLog module.
Cheers,
--
Sander van Zoest [EMAIL PROTECTED]
High Geek http://Sander.vanZoest.com/
Re: New proxy hook
On Mon, 22 Oct 2001, Pier Fumagalli wrote: And dinamically reconfigure your apache web server from an HTTP request? I am not sure if sending everything over HTTP is really such a good idea. It would be nice if it did not have unnecessary overhead and could integrate well with already build technology that is mainly used for remote configuration. Things like LDAP, WebDAV, DHCP/BOOTP and SNMP already have some of these qualities and allow you to configure/maintain things. If you allow reconfiguration via an HTTP request, then you start running into all sorts of race conditions. Your new configuration is going to effect your configuration update mechanism. I mean I do not use my vacuum cleaner to clean a vacuum cleaner. Dynamic configuration of something that is receiving this new configuration request seems unncessarily complex to me. -- Sander van Zoest [EMAIL PROTECTED] High Geek http://Sander.vanZoest.com/
Re: [PATCH] adding xml output to mod_status -- [REPOST]
On Tue, 2 Oct 2001, Mark J Cox wrote: What we ought to do is to first decide what the XML output is going to look like (it'll be a pain to change this later), then it doesn't really matter if it's a patch to mod_status or a new module. http://www.awe.com/mark/dev/mod_status_xml/example.xml I like the XML schema, but I would make a few minor adjustments. I would specify an httpd.apache.org xml namespace and a charset. Also spliting up the actual request into method, uri, protocol would it easier to manipulate those with xpath. I would also consider potentially using a different way to handle time such as NTP Timestamps and adding a numeric time zone. The current method works perfectly, but to do some mathematical calculations it might be useful to have it expressed differently. I will probably look into running this on my server soon. Cheers, -- Sander van Zoest [EMAIL PROTECTED] High Geek http://Sander.vanZoest.com/
