at Montag, 20. Juni 2005, Nick Kew wrote:
Hmmm. Is it better to have a UI that's openly a little more complex but
works as documented, or one that appears simple but has lots of
gotchas lurking in ambush? I guess that's an argument for mod_filter
implementing AddOutputFilterByType.
First,
at Sonntag, 17. April 2005, William A. Rowe, Jr. wrote:
The zip source tarball for win32, as well as the binary installers
for win32 (.exe and .msi) are available for testing from
http://httpd.apache.org/dev/dist/
and a few ack's or even a single nak would be appreciated.
Installed and
At 6. April 2005, Bill wrote:
WARJ At 12:53 PM 4/6/2005, Justin Erenkrantz wrote:
One last thought: do we really need 'UseCanonicalName Off' - isn't
our unset default equivalent? Same goes for HostnameLookups (the
unset default is Off). IMHO, these seem more appropriate for
httpd-default.conf.
I changed mod_imap this morning from 'yes' to 'most', because I was
tired of disabling it every time I do a new install. I think we
should reconsider what modules are enabled by default. Here is my
list of suggested changes:
mod_version: all - yes
+-0, no opinion
mod_asis: yes - no
'most'
JO Enabling UserDir by default can allow remote users to determine whether
JO a given username is valid on the system or not, even if no users have a
JO public_html directory, from the difference between a 403 from a chmod
JO 700 /home/realuser and a 404 from not finding /home/nosuchuser.
JO
FWIW: At this time there's no way to get me into the States, regardless of
which coast, sorry.
Same for me. :(
So a hackaton in the Netherlands or during the European ApacheCon would
be fine.
Kess
[EMAIL PROTECTED] Tuesday, November 16, 2004 4:29:31 PM
* Brad Nicholes [EMAIL PROTECTED] wrote:
During ApacheCon several httpd PMC members got together to discuss
current issues with the httpd project and to try to find better ways to
manage the project. One of the issues that was
There is another script (with the same back-end) that does almost this.
See, for example:
http://www.apache.org/dyn/closer.cgi/httpd/httpd-2.0.50.tar.gz
Cool. Is this script linked somewhere? Or there any description out
there at our site?
Kess
Ehm, would you mind to do the same for the httpd-docs-2.0 snapshot?
Done. Should be available on the next snapshot (roughly every 6 hours).
Yell if it doesn't work. -- justin
It does. Thank you very much.
Kess
I've tweaked cvs.apache.org's snapshot scripts to include branches. This
means that 2.0 snapshots (APACHE_2_0_BRANCH) will be generated alongside the
2.1 snapshots (HEAD).
Great idea. Thank you, Justin.
Ehm, would you mind to do the same for the httpd-docs-2.0 snapshot?
Kess
I was just asked again by a user about the load order of modules.
While it seems that it is now with Apache2 less important, and also
ClearModuleList and AddModule are removed now with Apache2, I think it
is at least still important for auth modules. So I searched the manual
for any hints,
Erik wrote.
On 06/09/2003, at 11:43, Astrid Keßler wrote:
Cliff wrote:
Yes, it would. But for a debug log it's a price I'm willing to
accept.
Just an unformed idea: allow these directives within Directory (and
Location?), but not within .htaccess files. The log file could be
opened
I guess the other one I'd like to see is rewritelogging/loglevel from
inside a .htaccess file.
It's a real bitch trying to debug rewrite rules inside this (and in
rules inside of directory/location blocks)
+1 for ScriptLog and RewriteLog(Level), although I'm not sure this is
easy to
Just to prevent any misunderstandings: are we talking about a 2.2
*alpha* or *beta* release here, or what will it be called? If it's in
any way marked as *unstable*, then a clear +1 from my side. The recent
changes are definitely worth to get tested in the wild, IMHO.
The alphas/betas will
erikabele2003/08/09 07:24:14
Modified:docs/manual/mod Tag: APACHE_2_0_BRANCH core.xml.de
Log:
Remove superfluous note; it's not in the english version. Kess, can you confirm?
eek, you are right. This is an accidental and overseen paste. Thank
you, Erik.
Kess
$prefix/build sounds more naturally to me.
+1.
+1
-Thom
+1
Kess
Did some of you have a binary for mod_ssl 2.0.47 Windows ?
There is a 'over-complete' pre-built Apache 2.0.47 package
including mod_ssl and OpenSSL 0.9.7b for Windows:
http://www.apachefriends.org/wampp.html
But be aware that it's fairly large, around 43MB. Didn't look
into it; just
It would be a big help to our users if config.nice was installed by a make
install.
This is a really good idea. +1
Kess
What about a second parameter to ErrorLog?
That's an interesting idea.
I can change ErrorLog to a TAKE12 to take an optional parameter so as not
to break existing configs. Is this method preferred to a second directive?
I can't tell, this is preferred or this is not preferred, espacially
On Thu, Jun 26, 2003 at 12:04:31AM +0200, Astrid Ke?ler wrote:
This adds a directive ErrorLogsWithVhost that extends the error log format
by adding server name and port to entries in the error logs.
This can also be done with LogFormat using %v and %p. What is
wrong with these log formats?
This adds a directive ErrorLogsWithVhost that extends the error log format
by adding server name and port to entries in the error logs.
This can also be done with LogFormat using %v and %p. What is
wrong with these log formats?
Kess
What about simply splitting the mails automatically at some threshold byte
count (of course, between single diffs)? Would that help? Would it be better
to receive, say, 6 x 100 KB, rather than 1 x 600KB?
I can't figure out a real advantage. It doesn't matter if I get one big
or many small
Hm, sorry.
I'd see some alternatives
- split the commit (e.g. by language)
- create a new docs-cvs-mailinglist
- drop the generated files and build the stuff online and for every release
(RM job, resp. the tarball roller's) - would need some MBs of Java stuff
installed everywhere
- ?
Hallo Thom,
Nachricht vom Friday, May 30, 2003, 1:05:12 PM:
* Astrid Ke?ler ([EMAIL PROTECTED]) wrote :
Hm, sorry.
I'd see some alternatives
- split the commit (e.g. by language)
- create a new docs-cvs-mailinglist
- drop the generated files and build the stuff online and for
First, I'm talking about changes in 2.1 only. I'm opposed against
changing the module status in 1.3 or 2.0, too. :)
In this discussion about default modules, I hear three different things:
1) compile a module by default (or what category, e.g most or all)
2) enable a module in the
1. This might be a good opportunity to go through the whole list and see
what should be in and out of a default build. For example, mod_expires
might be a good addition. Of course, I don't have time to do this myself
at the moment, so feel free to ignore this comment.
2. If we want to keep
-a directory. The allowed syntaxes are:/p
+a ressource. The allowed syntaxes are:/p
It's resource.
*oum* ... eh, yes, this is a typical german error. :-)
Thank you
Kess
The attached patch for modules\loggers\config.m4 changes the
--enable-logio default from 'no' to 'most', because I can't see any
reason for 'no'.
Kess
config.m4.patch
Description: Binary data
I looked at the status of some modules and found, that mod_logio won't
compile with 'most' modules (configure --enable-modules=most). Are there
any reason for?
Kess
E-Mail: [EMAIL PROTECTED]
On Tue, 4 Feb 2003 10:20:33 -0800, William A. Rowe, Jr. wrote:
An answer to a user question (and a gripe from me since I've hit this
problem myself on apache.org);
[the links] point to .tar.gz files, which exist. When they are clicked on,
however, they are being renamed to .tar.tar files.
On Wed, 22 Jan 2003 02:28:11 +0100, André Malo wrote:
* Joshua Slive wrote:
On Tue, 21 Jan 2003, Günter Knauf wrote:
Hi,
have modified the 1.3 patch against mod_autoindex to provide configurable colored
indexes for 2.0;
is this of any interest?
-0.
hmm, I don't have a strong opinion
On Sat, 18 Jan 2003 11:49:53 -0500 (Est), Joshua Slive wrote:
Looks good. Tiny gramatical error below.
-pThe file path specified may be a fully qualified path (i.e.
+pThe file path specified may be a absolute path (i.e.
That should be an absolute.
Oups, thank you, and
The documentation of the TimeOut directive contains the following:
The timer used to default to 1200 before 1.2,
but has been lowered to 300 which is still far more than
necessary in most situations. It is not set any lower by
default because there may still be odd places in the
+if (sconf-max_streaming_buffer_size sconf-min_cache_object_size) {
+ap_log_error(APLOG_MARK, APLOG_WARNING, 0, s,
+ MCacheMaxStreamingBuffer must be less than or equal to
MCacheMaxObjectSize.
+ Resetting MCacheMaxStreamingBuffer
34 matches
Mail list logo