Karsten Engelke wrote:
My idea was to include a complete set of custom error messages in
many different languages with Apache.
ISTR this was brought up on the apache-docs mailing list
a few weeks ago, too. And I think Lars was involved in the
discussion..
--
#kenP-)}
Ken Coar,
Ryan Bloom wrote:
The reality is that most people just use the default
config, and modify it to fit their needs.
I think that actually the reality is that most people
get a massaged config as part of their OS distribution,
which probably bears only a nodding resemblance to our
file. The
Well, if Novell (who support it) feel that way, I'm inclined
to say 'provide replacement text to be checked in.'
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
All right everyone! Step away from the
William A. Rowe, Jr. wrote:
That is, if the URI is index.bak, we can only negociate
amongst variants matching index.bak* -- NOT index.*.bak*.
What's your rational? I agree that index[.*].bak[.*] is broader
than index.bak[.*] --- but I'm wondering why you feel this way?
Say that we
I know I was one of the last holdouts that used the old
src/Configure method, before being converted to APACI.
Which suddenly makes me wonder.. is there *anyone* that
still uses src/Configure? Does anyone know if it still
works? :-)
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/10/03 18:39:38 $]
Release:
1.3.21: In development - Bill Stoddard has proposed a TR soon,
(tag scheduled 10/3 2330Z or thereabouts)
1.3.20: Tagged and rolled May 15,
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2001/10/03 17:47:50 $]
Release:
2.0.25 : rolled August 29, 2001
2.0.24 : rolled August 18, 2001
2.0.23 : rolled August 9, 2001
2.0.22 : rolled July 29, 2001
2.0.21 :
Ryan Bloom wrote:
This patch completely deprectates the Port directive.
The ServerName directive is now overloaded, so that
admins specify the port and name on the same directive.
It also makes Listen a required directive.
I must have missed something. Just WTH is the motivation
for all
William A. Rowe, Jr. wrote:
Now our users have exactly _two_ directives to comprehend:
Listen controls what addresses and ports the server listens on;
ServerName defines the server's OWN name for itself, including
it's port if it is a nonstandard assignment;
All right, got it.
And
Bill Stoddard wrote:
Good message from Mark that is worthy of discussion...
I think there's one tweak needed in mod_auth.c..
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
All right everyone! Step away
Testing the build on RH 6.2 with -Wall -Wshadow:
1. '/*' inside a comment in proxy_http.c:477
2. -Wshadow shows some warnings in ab.c (thought those were all
cleared up?).
3. I wish we could fix that bloody http_config.h:98 'function
declaration isn't a prototype' message..
About to
[EMAIL PROTECTED] wrote:
Guys... please be _careful_ when you pcalloc - palloc!!!
:
+else
+base-response_code_strings = NULL;
+
And please abide by the style guide:
else {
base-response_code_strings = NULL;
}
--
#kenP-)}
Ken Coar,
Not acked. I suspect he's got a language selection
thing going.. but it might also be a consequence of
the recent 2.0 negociation issues, since apache.org is
running 2.0 test code.
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist
hiten pandya wrote:
i jus' converted the whole of the apache documentation into
two more formats:
- a postscript version of the document
- and pdf (portable document format)
if u think this is the wrong place for asking this question..
please give me its main place for asking the
I just noticed that the responses coming back from www.apache.org
seem to have lost the charset attribute we were tagging on everything.
URL:http://www.apache.org/docs/, for instance, says
Content-type: text/html
instead of
Content-type: text/html; charset=iso-8859-1
Is the
William A. Rowe, Jr. wrote:
Looking at http://httpd.apache.org/docs/ which I believe you ment;
Yar, that's what I meant.
Which directive did you expect to behave which way?
Marc has already answered this.
And precisely how do you mean Marceau-ian.
As in Marcel Marceau, a celebrated
William A. Rowe, Jr. wrote:
Well, er, no. What Apache Configuration Directive did
you expect was set in the .conf file that would cause this
to behave as you had expected.
I mentioned it in my first note:
or simply a missing DefaultCharset directive
And as for whether always adding a
William A. Rowe, Jr. wrote:
To be RFC compliant we must start by fixing today's wrong behavior.
User accepts .en and .fr at q=.5, server chooses one
[WRONG: MULTIPLE_CHOICES should be presented!!!]
Both of those are at q=0.5, or only .fr?
User accepts no specified, we serve none [Also
William A. Rowe, Jr. wrote:
Apropos of nothing. Given a request with no language, yes,
it will serve. But in the grand scheme, .html.html aught be
treated as whatever one sets their DefaultLanguage to, which
would undermine the original workaround.
And if there is NO DefaultLanguage?
[EMAIL PROTECTED] wrote:
The core input filter would happily consume all the data
you gave it in a header line, looking for that one LF.
This patch limits that getline functionality to
HUGE_STRING_LEN (8192 bytes).
Shouldn't that use the value from the LimitRequestFieldSize
directive
Greg Ames wrote:
* The core input filter has no idea if it's working on
a request line or header line.
Then I consider this perilously close to a showstopper
for GA; the Limit* directives, which were added for a
reason, appear worthless -- an unacceptable regression.
Does even
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/10/29 06:20:47 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2001/10/31 07:18:47 $]
Release:
2.0.27 : tagged October 30th, 2001.
2.0.26 : tagged October 16th, 2001. not rolled.
2.0.25 : rolled August 29, 2001
2.0.24 : rolled August 18,
Cliff Woolley wrote:
tested with httpd-test HEAD, failed some tests:
Failed Test Status Wstat Total Fail Failed List of failed
-
apache/limits.t 102 20.00% 7, 9
I don't consider this one a
Jeff Trawick wrote:
How many people really give a shit? I'm truly curious.
I do. It irritates me and detracts from my concentration when
I'm scanning code and then have to go back and look more carefully
because some bloody brace wasn't where it was supposed to be.. or
an if-enclosure is
Jeff Trawick wrote:
How many people really give a shit? I'm truly curious.
..whoops.. but I don't think it's a show-stopper for a release.
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
All right
[EMAIL PROTECTED] wrote:
Drop the wide net observed by Ken Coar, since one .rc file does exist
in cvs (and should reside there.)
:
Release
Debug
+ApacheMonitorVersion.rc
+wintty.rc
*.plg
*.aps
*.dep
*.mak
-*.rc
So why did you say that's the
Cliff Woolley wrote:
The sigh was sigh I'm so anal-retentive it's ridiculous
That's not so bad. When you don't dare sit down for fear that
you'll suck up the furniture, now *that's* anally-retentive.. :-)
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author,
Here's another one (APR, really).
apr/docs contains canonical_filenames.html
However, apr/docs/.cvsignore contains *.html which
means this file is to be ignored.
Is it supposed to be ignored or not? If so, someone
should cvs rm it. If not, the .cvsignore file is in
error.
The file shows up
Aaron Bannert wrote:
Hmm...This was my main concern. Is there any way we can
make suexec's docroot relative to the ServerRoot (determined
at runtime)?
I have a partially completed patch somewhere that allows
for multiple acceptable docroots to be specified at
configuration/compile time,
Ryan Bloom wrote:
I don't see why we can't. The code needs to be reviewed
whether the code is submitted with a name or not.
One word: liability. Two more: patent infringement.
I think we need some evidence of good faith that the
code isn't encumbered, or else it can't get any closer
than
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/11/10 20:30:54 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2001/11/21 18:19:06 $]
Release:
2.0.29 :
2.0.28 : released November 13, 2001
2.0.27 : rolled November 6, 2001
2.0.26 : tagged October 16, 2001. not rolled.
2.0.25 :
* On 2001-11-22 at 10:38,
[EMAIL PROTECTED] [EMAIL PROTECTED] excited the electrons to say:
DO NOT MAKE CHANGES ON THE LIVE SITE!!!
Some things have to be checked/tested in situ. If the
admonition is to not leave uncommitted changes on the live
site, that's a +1.
--
#kenP-)}
Ken
* On 2001-11-24 at 18:49,
Rodent of Unusual Size [EMAIL PROTECTED] excited the electrons to say:
I didn't get Ian's original message (?), but it looks as
though 2.0.28 is failing the same includes tests. Verifying
now..
Yep, 2.0.28 is also failing some of the includes tests
Ryan Bloom wrote:
On Friday 23 November 2001 09:18 am, Ian Holsman wrote:
try backing out ryan's change to core.c which was made a couple of days
ago. That should fix the mod-include problem.
I didn't get Ian's original message (?), but it looks as
though 2.0.28 is failing the same
Sander Temme wrote:
Index: src/Configure
===
RCS file: /home/cvspublic/apache-1.3/src/Configure,v
retrieving revision 1.444
diff -u -r1.444 Configure
--- src/Configure 2001/10/08 20:59:36 1.444
+++ src/Configure
Liu Wen wrote:
*CVS exited normally with code 0*
Um, that usually means that it was *successful*, not that
it failed..
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
All right everyone! Step
Ryan Bloom wrote:
On Saturday 24 November 2001 03:55 pm, Rodent of Unusual Size wrote:
* On 2001-11-24 at 18:49,
Yep, 2.0.28 is also failing some of the includes tests as they
currently exist in httpd-test/perl-framework. However, those
are real failures, not protocol errors, so
Acked.
- Forwarded message from acid-byte [EMAIL PROTECTED] -
From: acid-byte [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Windows XP
Date: Wed, 14 Nov 2001 02:21:57 -0500
I'm currently using Windows XP Pro and was wondering if the Windows
distribution has been tested on this OS as
Rodent of Unusual Size wrote:
Acked.
Um, that means the original sender isn't on this list -- so
if you have info for him, you need to explicitly cc him on
your messages..
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http
'Way back in May 2001, Phil Dietz proposed adding the ability
to control whether the file inode should be included in the
formulation of a document's ETag. He originally proposed it
as an extension to the Options directive, but said he'd re-do
it as its own directive. I can't find any record of
Roy T. Fielding wrote:
Good idea -- I was trying to keep the most relevant part of the name
at the front so that it is easy to find in the documentation, but
FileETagValue is better than the alternatives. Actually, just FileETag
(with one option being none) would be best.
And how should
Rodent of Unusual Size wrote:
The former (omit the ETag field from the response header) will
require a MMN bump
Well, maybe not -- not if I don't mind polluting ap_send_header_field()
with knowledge about what it means and how to figure it out..
--
#kenP-)}
Ken Coar
I'm getting this when I try to build Apache 2.0.* on Red Hat
Linux 5.2 (libc5, I think):
###Test: Platform: Linux 2.0.36 i586 unknown
###Test: Removing files from previous test run
###Test: Creating working directory /var/tmp/ap2-test
###Test: Locking work area: done.
###Test: Working with CVS
William A. Rowe, Jr. wrote:
Consider yours to be the first comment in several months
even _noticing_ the change...
Well, I'm updating some docco on download-and-build scenarios,
and here it is changed from how we used to do it.. At least now
I know why, regardless of what my opinion is.
--
William A. Rowe, Jr. wrote:
I meant to say [to be absolutely clear] that the decision
was unilateral due to the two 'majority scenarios' below,
the interest in conserving absolutely wasted collab donated
bandwidth [not to mention our mirror friends], and the last
bugaboo I discovered.
William A. Rowe, Jr. wrote:
So I started to look at how we distribute source in other
binary packages.
You mean other ASF packages, other open-source packages, or
specifically the httpd project packages?
While reviewing those changes to the 2.0 package, I looked
at how we package both 1.3
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/11/10 20:30:54 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2001/12/05 16:51:50 $]
Release:
2.0.30 : In development
2.0.29 : tagged November 27, 2001
2.0.28 : released November 13, 2001
2.0.27 : rolled November 6, 2001
2.0.26 :
Changing the contents of packages that have Apache's name
of them should be a group decision, IMHO.
That said, the /dist/httpd/ tree contains over 500MB.
About 65% of that is in binaries/, and most files in
there contain the source and a small delta (the binary
proper). It seems reasonable to
Pål Baltzersen wrote:
So I made this little patch that sets the env REMOTE_GROUP to
the group (first match) a user was authenticated with. I think
the performance penalty is microscopic.
There are some problems with this patch:
1. It munges the middle of the conn_rec structure, breaking
[EMAIL PROTECTED] wrote:
Our question is the following: We've an Excel sheet and we
communicate with it by the COM object from PHP.
This is not a support list. Please see
URL:http://httpd.apache.org/userslist.html.
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
William A. Rowe, Jr. wrote:
3. Namespace polution is evil. Ergo, any module should reject requests
for a document with path_info if it doesn't address the name space
passed in path_info for the request.
Can you explain this in different words? And/or maybe an example?
--
#ken
William A. Rowe, Jr. wrote:
But if you never use path_info, it should be rejected to
prevent exactly this sort of polution/infinite recursion.
Ah, so you're suggesting that anything that actually maps
a URI to a document, but which doesn't do anything with
path-info, should return 404 if the
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/11/10 20:30:54 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
Brian Pane wrote:
Those definitely look bad. Do you have a way to get a stack
trace for one of these traps?
Dunno; this was during the RH-6.2-alpha testing (see
URL:http://Source-Zone.Org/Apache/regression/), and
I don't know whether it was during the build, the run,
or what. Since this is
Greg Ames wrote:
Rodent of Unusual Size wrote:
These showed up in my kernel log from a build of HEAD
httpd-2.0?
Yep. Sorry, I meant to mention that. It melted in my
head, and not in my hand.
I'm pretty sure these are wicked expensive in terms of things
like the instruction cache
Theo Schlossnagle wrote:
You didn't make it clear that you were using Linux
Yes I did:
These showed up in my kernel log from a build of HEAD
on RH Linux 6.2 on Alpha, using GCC egcs-2.91.66.
So the Compaq C compiler issue is a non-starter. This is
all gcc stuff.
--
#kenP-)}
Ken
Is there any supported way for a 1.3 module to be able to tell
whether the server is running in -X mode? The only one
I can think of is to declare both an init and a child_init
handler, and check at a later stage to see whether the
child_init ever ran..
How about for 2.0?
--
#kenP-)}
Ken
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/12/18 15:31:57 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2001/12/17 22:05:58 $]
Release:
2.0.30 : In development
2.0.29 : tagged November 27, 2001
2.0.28 : released November 13, 2001
2.0.27 : rolled November 6, 2001
2.0.26 :
[EMAIL PROTECTED] wrote:
-/^[ \t]*AP[RU]?_DECLARE[^(]*[(][^)]*[)]([^ ]* )*[^(]+[(]/ {
-sub([ \t]*AP[RU]?_DECLARE[^(]*[(][^)]*[)][ \t]*, )
+/^[ \t]*AP[RU]?_(CORE_)?DECLARE[^(]*[(][^)]*[)]([^ ]* )*[^(]+[(]/ {
+sub([ \t]*AP[RU]?_(CORE_)?DECLARE[^(]*[(][^)]*[)][ \t]*, )
Gary Benson wrote:
I found a bug whereby Apache 1.3.22 inconsistently handles
the interaction between aliases to non-existant paths and
authentication. If the alias is specified as an absolute
path then a 401 is always served, but if the alias is a
relative path then in some cases a 404
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/12/18 15:31:57 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2001/12/26 13:20:02 $]
Release:
2.0.30 : In development
2.0.29 : tagged November 27, 2001
2.0.28 : released November 13, 2001
2.0.27 : rolled November 6, 2001
2.0.26 :
Aaron Bannert wrote:
Having some problems with the images, I think the spaces are freaking
out my Linux/Netscape browser.
Indeed. Embedded spaces are illegal; the page that links to
the images needs to use encoding like 'Transport%20Error%20Analysis.gif'.
Curiously enough, '%20' encoding
[EMAIL PROTECTED] wrote:
RELEASE SHOWSTOPPERS:
[snip]
* Test suite failures:
o perchild doesn't even build
Well, it builds on Red Hat 5.2 now, but doesn't start
(or at least keep running) with the perl-framework's
default configuration. And it doesn't even build
on Red
William A. Rowe, Jr. wrote:
Prior to tag, we use perl-framework to actually check that the
current server is fully operational [as defined by our wonderful
test-dev group!!!]
I have this running automatically, on a nightly basis, for
worker, prefork, and perchild. The tests run on Red Hat
William A. Rowe, Jr. wrote:
Another side issue that I notice; we should _REALLY_ be
presenting MULTIPLE CHOICES rather than serving the smallest
file. The smallest file -hack- is exactly that, someone
worthless for reasons debated on this list many times.
If you are referring to the past
Bill Stoddard wrote:
SetEnvIf ^TS* ^[a-z].* GET_TIMESTAMP
Header echo ^TS*
If these are REs, shouldn't that be ^TS.*, at least in the
first one?
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/12/18 15:31:57 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2002/01/02 19:34:47 $]
Release:
2.0.30 : In development
2.0.29 : tagged November 27, 2001
2.0.28 : released November 13, 2001
2.0.27 : rolled November 6, 2001
2.0.26 :
[sent last night, looks like it didn't get through..]
I don't know how many people use Emacs to edit the Apache stuff,
but would anyone object to a stanza at the bottom of the source
files to help put Emacs in the right stylistic mood? To wit,
something like:
/*
* Local Variables:
* mode: C
Bill Stoddard wrote:
-1 (and I'm an emacs user :-)
Metadata should be kept seperate from data. I.e., you should
put something like this in your _emacs file :-)
Which a) would need to be done by every Emacs user individually,
and b) new users would know nothing about.
Whatever. It just
I don't know how many people use Emacs to edit the Apache stuff,
but would anyone object to a stanza at the bottom of the source
files to help put Emacs in the right stylistic mood? To wit,
something like:
/*
* Local Variables:
* mode: C
* c-file-style: bsd
* indent-tabs-mode: nil
* End:
Ryan Bloom wrote:
I'm in favour of a mechanism that doesn't require every single
generated-content module to be rewritten to include an essentially
duplicate function.
I'm in favor of doing this in the code and not forcing every
administrator to reconfigure their server to get this
Bill Stoddard wrote:
However, I think we should provide something to allow 3P
module usage to avoid the stats without requiring that
*they* be rewritten.
I disagree with the last sentence. We should not complicate
the configuration of the server more than it already is to
accomodate
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/12/18 15:31:57 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
So.. should this be changed to
1. no MMN bump,
2. a minor MMN bump,
3. a major MMN bump, or
4. reverted right out of 1.3?
I'm personally cool with any except #4..
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist
William A. Rowe, Jr. wrote:
From: Roy T. Fielding [EMAIL PROTECTED]
Sent: Thursday, January 10, 2002 5:47 PM
And no features should be added to 1.3 without the parallel patch to 2.0,
if it is at all relevant. Ken, is there a patch forthcoming?
You betcha. Docco too. :-)
Okey, MMN bump
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2001/12/18 15:31:57 $]
Release:
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config mismatch. t/r Oct 5, 2001)
APACHE 2.0 STATUS: -*-text-*-
Last modified at [$Date: 2002/01/15 19:16:01 $]
Release:
2.0.31 : In development
2.0.30 : tagged January 8, 2002.
2.0.29 : tagged November 27, 2001. not rolled.
2.0.28 : released November 13, 2001
Acked.. but not yet fixed.
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/
Author, developer, opinionist http://Apache-Server.Com/
Millenium hand and shrimp!
---BeginMessage---
I'm an OSX user and am using fink to update my apache installation.
It appears
Bill Stoddard wrote:
Tagged.
Breakage:
CC=gcc \
CFLAGS=-g -O2 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow \
./configure --enable-shared=max --enable-module=most
:
make
:
gcc -c -I../../os/unix -I../../include -DLINUX=22 -DNO_DBM_REWRITEMAP -DUSE_HSREGEX
Thomas Eibner wrote:
ln -s /usr/include/gdbm-ndbm.h /usr/include/ndbm.h in case
you're running debian and have installed libgdbmg1-dev.
(If that is the case: debian breakage by default, not apache's fault)
A /usr/include/gdbm/ndbm.h file exists. Adding symbolic
links all over the
Joe Orton wrote:
This will happen if you don't have the db1-devel package installed
(unsurprisingly: if the header isn't there, it isn't detected). If you
do have db1-devel installed, you should find -I/usr/include/db1 in your
CFLAGS...
So what's the /usr/include/gdbm/ndbm.h file all
Thomas Eibner wrote:
On Mon, Jan 21, 2002 at 04:15:25PM -0500, Rodent of Unusual Size wrote:
A /usr/include/gdbm/ndbm.h file exists. Adding symbolic
links all over the /usr/include tree is *not* an option if
other packages don't have a problem with finding it.
But you're
Thomas Eibner wrote:
Moving around on the way that find-dbm-lib looks for the libs works for
me on my Debian box. Is this going to break something else?
Without testing this patch (my 7.1 system just hung again),
wouldn't we have to fix the CFLAGS to include -I/usr/include/gdbm,
though?
--
Thomas Eibner wrote:
Like this? I had to put the gdbm test after db1 since debian only has
the gdbm-ndbm.h (but it has the db1/ndbm.h)
Yep, that does it -- at least on the RH 7.1 system; haven't
tried it on others. -Wall -Wmissing-prototypes generates a
bunch o' messages for ndbm.h, but the
From a private emessage someone sent me:
Is there a way to use SetEnvIf or SetEnvIfNoCase to detected the
presence of a particular HTTP header line (possibly an experimental
header line such as X-Exp-Header: special-request) to trigger an
external output filter using SetOutputFilter?
In
APACHE 1.3 STATUS: -*-text-*-
Last modified at [$Date: 2002/01/21 19:34:31 $]
Release:
1.3.23: Tagged Jan 21, 2002.
1.3.22: Tagged Oct 8, 2001. Announced Oct 12, 2001.
1.3.21: Not released.
(Pulled for htdocs/manual config
I think I forwarded a message about this..
I just tried to fetch the 1.3.22 tarball, and here's what
I got:
$ wget -c http://www.apache.org/dist/httpd/apache_1.3.22.tar.gz
--20:37:54-- http://www.apache.org/dist/httpd/apache_1.3.22.tar.gz
= `apache_1.3.22.tar.gz'
Connecting to
httpd, htpasswd, htdigest, and the other main applications need
to be built with static libraries. In other words, they must
not be linked against libapr.so and friends.
Why? Because otherwise we make life difficult for users, and
make violation of the Principle of Least Astonishment a virtual
Jeff Trawick wrote:
Ken's talking binbuild...
For what we distribute, certainly. But I think static
libraries should also be our default. Otherwise someone
who builds from scratch is going to run into the same
astonishment when it tries to copies home-built files
around. It'll look like it
Jim Jagielski wrote:
2. Why aren't the 1.3.22 tarballs available somewhere in the
dist tree? Jim?
Should they be? If any place, they should be in a subdir, and not
in the main dist level, IMO.
They sure should be. For example, right now people have nothing
to download to put
From something that happened a couple of days ago on Daedalus..
The parent died, but the children hung around. That shouldn't
happen, and is a showstopper (but I'm not listing it as one
yet in case I'm missing something).
If the parent dies, shouldn't the children get the equivalent
of SIGPIPE
Bill Stoddard wrote:
In addition to the cgid daemon pool, I also believe we need
Jeff's retry logic. The combination should provide good
performance and robustness.
And if we exhaust the retries, throw a 503 rather than a 500.
--
#kenP-)}
Ken Coar, Sanagendamgagwedweinini
Aaron Bannert wrote:
I've already added this for our various support binaries:
--enable-static-htpasswd
Having to explicitly specify this to make it happen is not on;
it needs to be the default. Having to specify for each individual
util is also bogus; there should be a switch, defaulting
They are in httpd-docs-1.3/apidoc/. So looks like apache-devsite
needs a trival link fix
apache-devsite is dead. I've done the right things to get
the API dictionary back online, at
URL:http://httpd.apache.org/dev/apidoc/.
Thanks for pointing it out..
--
#kenP-)}
Ken Coar,
701 - 800 of 1314 matches
Mail list logo
