Jeff Trawick wrote:
Geoffrey Young wrote:
wow, I didn't expect to see this followed up upon. thanks.
Server version: Apache/2.1.0-dev
Server built: Aug 12 2003 02:25:22
Server's Module Magic Number: 20030213:1
Architecture: 32-bit
Server MPM: Prefork
too bad ap_show_mpm doesn't list
wow, I didn't expect to see this followed up upon. thanks.
maybe httpd developers should be stranded in airports more often...
also, several weeks ago somebody was complaining to me about various
things they didn't like about Apache 2... one of the ones I took note of
was having httpd
I'll work on the real httpd -V
stuff later this afternoon.
here is the latest patch. basically, it's the same as what I submitted
before. the differences are those suggested by stas and jeff - make the
AP_MPMQ_STATIC/DYNAMIC wording a bit better and axe the -D APACHE_MPM_DIR=
stuff.
so, the
IfThreaded
MaxThreadsPerChild 5
/IfThreaded
This rubs me the wrong way FWIW.
oops, sorry :)
I think it is best to have all
directives for a specific MPM together in one container, and have that
container specific to the MPM.
well, in some cases I'd certainly agree.
William A. Rowe, Jr. wrote:
At 02:10 PM 12/3/2003, Geoffrey Young wrote:
IfThreaded
MaxThreadsPerChild 5
/IfThreaded
This rubs me the wrong way FWIW.
oops, sorry :)
I don't care for that container either... but even horrible new ideas
are always good when then generate
commited to 2.1-dev... thanks!
sure. and thanks for taking the time to shepherd it through.
--Geoff
Actually, such defines might need to be a little more dynamic, but either
IfDefine AP_MPM_THREADED would be good, or if we absolutely
needed too, we could add IfFeature FOO where features could be
registered, by the core or by a loaded module.
to that end, here's a preliminary and rough
Paul J. Reder wrote:
This patch addresses PRs 24884 and 25123. Please see my note at
http://marc.theaimsgroup.com/?l=apache-httpd-devm=106947094322141w=2
for a full explanation of the problem with code references.
I've griped a bit before about having default_handler make conditional GET
hi all...
currently, all core container directives have an issue (albeit a minor one)
- they require an argument in practice but are allowed to proceed without
one during configuration.
for example
IfModule
does not currently throw an error. instead, the config is allowed to
proceed, soaking
André Malo wrote:
* Geoffrey Young [EMAIL PROTECTED] wrote:
anyway, attached is a patch that makes IfModule, IfDefine,
I'd like to keep IfDefine possible. Simply because it's a very efficient
way to comment a whole part out (reliably, since one cannot specify an
empty -D argument
Jeff Trawick wrote:
Geoffrey Young wrote:
I've griped a bit before about having default_handler make conditional
GET
decisions, and this is probably another instance where having
ap_meets_conditions in it's own filter could avoid inevitable problems.
I'm up for laying out my issues
Stas Bekman wrote:
Geoffrey Young wrote:
[...]
hopefully, this kind of makes sense to at least some people. personally,
the only thing that makes sense to me is moving conditonal GET logic
to it's
own filter, similar to Content-Length I suppose. yes, it would slow down
the server
Geoffrey Young wrote:
André Malo wrote:
* Geoffrey Young [EMAIL PROTECTED] wrote:
anyway, attached is a patch that makes IfModule, IfDefine,
I'd like to keep IfDefine possible. Simply because it's a very efficient
way to comment a whole part out (reliably, since one cannot specify
William A. Rowe, Jr. wrote:
At 09:36 AM 12/9/2003, Geoffrey Young wrote:
André Malo wrote:
I'd like to keep IfDefine possible. Simply because it's a very efficient
way to comment a whole part out (reliably, since one cannot specify an
empty -D argument). And it's in use out there.
ok, here
[EMAIL PROTECTED] wrote:
trawick 2003/12/10 14:40:33
Modified:.CHANGES
server core.c
Log:
Fix Limit and LimitExcept parsing to require a closing ''
in the initial container.
PR:25414
Submitted by: Geoffrey Young
Now you have me thinking. For Apache 2.1 (perhaps 2.0) I'd like to see that
particular nonsense go away. I sympathize with André's observation that it's
useful, but what he wants to do can be accomplished with
IfDefine NEVER
DangerousDirective
/IfDefine
which serves the same purpose, but
the way Apache chose to work around this was to add the filter_init
callback
to allow filters to add processing just prior to content generation.
presumably, this is where filters could call ap_update_mtime or
whatnot to
add their information in the conditional GET calculations. the
hi all
this is something I've been meaning to do for a while. as mod_include
demonstrates, output filters will sometimes be required to remove the ETag
header generated by content handlers, depending on how much they alter the
content. the current methodology is to set a no-etag note, which is
Paul J. Reder wrote:
I just have a quick comment based on some work I did recently.
You should check for the ETag value in both headers_out locations.
It is actually a bit more likely that the ETag will be in
r-err_headers_out
rather than r-headers_out, but it could be in either.
hmm, I
thanks for your input - new patch attached.
bah, that's not right either. I'll refactor it again and fix some of the
messed up logic over the weekend. sorry to waste the bandwidth.
--Geoff
William A. Rowe, Jr. wrote:
Just a quick tangent on weak ETags
let's say I have a transform to convert (charset-any) into utf-8 format...
and based on a browser string, conditionally insert that filter.
It's a straightforward (predictable) transform so that it retains any strong
hi again...
ok, I think I've worked out all the issues - attached is a new patch with
logic (and spelling :) errors hopefully worked out. also included is a
patch against the perl-framework for testing if you so choose.
one of the issues that needed working out was dealing with multiple ETag
Roy T. Fielding wrote:
one of the issues that needed working out was dealing with multiple ETag
headers. my original idea was to have ap_weaken_etag guarantee that ETag
headers would be weak. with ETag headers entering err_headers_out via a
third party, there exists the possibility that
sufficient interest in changing the current
(somewhat broken) core container args parsing, I'll just lop it off of my
todo list.
--Geoff
(current patch viewable from
http://nagoya.apache.org/bugzilla/showattachment.cgi?attach_id=9526)
Geoffrey Young wrote:
Now you have me thinking. For Apache 2.1
hi again...
I was wondering if much thought has been given to official thread and/or
process termination APIs. I tried sloshing through the archives but didn't
find much discussion.
I understand why ap_child_terminate was removed (or at least I think I do).
however, having something like
William A. Rowe, Jr. wrote:
It is almost worth a totally different hook entry point (before
post_config) such as vhost_init which *would* be called per-vhost
(starting from the main server config and working through the list.)
I have several modules with the for (s=_server; s; s = s-next)
William A. Rowe, Jr. wrote:
Only question below is should this hook always run before or after the
post config hook? My gut says after post config.
just going from what you had said earlier:
It is almost worth a totally different hook entry point (before
post_config) such as vhost_init
No... the default server is still a server. But you make an interesting point, that
certain percolation occurs in the post config. I suppose I would want that to
happen before my handlers dealt with the per-vhost settings, and I would not
want the changes I make to that global server to
Stas, we have closed a well known and remotely exploitable security leak. This
goes straight over comfort. If you don't like it, provide an alternative
solution. Just nagging or trying to talk the problem away doesn't help.
is creating a compile-time flag to disable the new-default behavior a
André Malo wrote:
* Stas Bekman [EMAIL PROTECTED] wrote:
Though since it really affects any logging it probably should be called
UNESCAPED_LOGGING or similar. And probably a similar patch applied to 1.3.
It only affects error logging.
that was my intent.
What do you mean by any
+ *) Allow unescaped error logs via compile time switch
+ -DAP_ERROR_LOG_UNESCAPED.
+ [Geoffrey Young geoff modperlcookbook.org, André Malo]
ah, cool :)
if it's all the same to everyone, I actually like joe's suggested
-DUNSAFE_LOG_ESCAPING (or some error_log derivitave) a bit
* unescaped error logs seem to be essential for some folks
backport -DAP_UNSAFE_ERROR_LOG_UNESCAPED to 2.0 and 1.3
server/log.c: r1.139, r1.140
-+1: nd
++1: nd, stas
should this get another vote, I have patches for 2.0 and 1.3 ready.
--Geoff
Index:
...which is the same way we enable mod_status and mod_info. The key
thing here is that the URIs to access a Location enabled handler do not
map to the filesystem, so the directory walk is a waste of cycles. So
what can we do about it?
isn't that what map_to_storage is for?
Bill Stoddard wrote:
mod_status and mod_info both are enabled via Location containers.
mod_status never DECLINEs if it is the handler. mod_info DECLINEs if
the method isn't GET. Let me see what happens if I send mod_info some
other method.
My not so well formed thoughts are that if a
hi all...
well, I haven't quite figured out all the weak etag issues yet, but just the
other day someone asked how to remove ETag headers from a default-handler
response.
so, I thought I'd re-submit the ap_suppress_etag() part as a formal API
wrapper around
apr_table_setn(r-notes, no-etag,
does anyone have any objections to applying this in 2.1?
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22299
--Geoff
André Malo wrote:
That has been long time on my todo (hello Stas! :-)
There's a new module I'd like to add to the core distribution. It makes use of
the new httpd version query function (ap_get_server_revision). It introduces
IfVersion containers, where you can depend your config on a
Well, thank you both. If there come no objections, I'll commit it these days
into modules/metadata.
actually, while I still like the idea, does it make sense to broaden the
scope of the module a bit? I had started a discussion on IfThreaded,
which turned into more of an IfServerIs ... idea
hi all...
hopefully I followed protocol here correctly wrt 2.1, but someone please
feel free to set me straight if I didn't.
I also closed the PR.
--Geoff
[EMAIL PROTECTED] wrote:
geoff 2004/01/30 11:43:39
Modified:.CHANGES
Log:
Keep focus of ITERATE and ITERATE2
That's fine. The only comment I have is that you should commit the
change to CHANGES and the core change at the same time rather than
splitting them into two separate commits.
yeah, I always try to do that, but my cvs client doesn't ever seem to pick
up on the Changes file (for any of my
hi all
it's come up a few times for me (and other users) that string-type
ErrorDocuments and custom responses default to text/html. however, lots
of people are using servers for xml-only content and want to be able to set
custom responses to simple xml strings without the overhead of a full
That introduced a warning to the 2.0 build:
mod_expires.c: In function `set_expiresbytype':
mod_expires.c:365: warning: passing arg 1 of `ap_strrchr' discards qualifiers from
pointer target type
the next version up in HEAD contains the fix
yes, I was just about to post this :)
:)
(thank goodness for cron)
and -Werror :)
so I guess that makes at least two who build nightly. just out of
curiosity, is anyone else?
--Geoff
Let's do this in 2.1 by splitting out the file system,
and if the filesystem module isn't handling a request, it won't be serving
content but also won't be invoking the directory walk or stat-ing files.
this all sounds kinda interesting, and similar to the way auth has been set
up in 2.1 -
Brian Akins wrote:
Any reason Apache does not allow this:
SetEnv ORIGIN 1234
SetEnv doesn't really set the environment by itself. by itself, it sticks
ORIGIN in the subprocess_env table during fixups. later modules (like
mod_cgi) make calls during content-generation to propagate the
Philippe M. Chiasson wrote:
As can be seen with this simple config file:
IfDefine not-defined
Location
/Location
/IfDefine
$ httpd -f broken.conf
Syntax error on line 1 of broken.conf:
Expected /Location but saw /Location
Location with no arguments is a bug in and of itself and
Philippe M. Chiasson wrote:
As can be seen with this simple config file:
IfDefine not-defined
Location
/Location
/IfDefine
$ httpd -f broken.conf
Syntax error on line 1 of broken.conf:
Expected /Location but saw /Location
ok, I tested your patch against the perl-framework and ran a
currently, mod_auth_basic and mod_auth_digest behave inconsistently
in some cases. for example, if i enter a wrong user/pw combination,
mod_auth_basic writes the following logline (i.e. without a username)
...
another inconsistency would be that if the authentication provider
reports and
Will Lowe wrote:
It looks like byte-range requests on non-existant files returns 206
instead of 404 if ErrorDocument is set.
I was able to verify this - it looks like there's some simple logic in 2.0
that wasn't carried over to 1.3.
so, try this patch. all the byterange tests in the
Mathihalli, Madhusudan wrote:
Here's a slightly modified version of Joe's patch to
- not segfault if rewrite_ssl_var_lookup is not available (mod_ssl not loaded)
- use SSL environment variables as %{ENV:HTTPS} or %{ENV:SSL_PROTOCOL}
I tested the patch with the following rules, and it
Maybe
we should put the HTTPS check into an own function (we could use %{HTTPS} in
mod_rewrite then). That way, other modules, that want to check (only) HTTPS,
also don't need to run though all the mess of ssl_var_lookup.
I'm not familiar with mod_ssl internals, but is there any reason we
If you have a concrete example of something that needs to query the state,
then we can examine whether it should hook into the processing
differently. I bet there is a different hook or approach that can avoid a
query of the state.
I think where stas is headed are cases like ryan's
Will Lowe wrote:
Thanks for the quick response -- sorry I've been slow getting back to
you. Yes, the attached patch does seem to fix 1.3.X. It'd be great if
it got rolled into the next point release.
ok, I'll try and guide it through the process.
--Geoff
hi all. a few win32 things :)
I'm trying to get 2.0.48 to compile using VC++ 5.0 (sp1) on win2k (sp4) and
am having a few issues. yeah, I know it's old, but I happen to have it
around and it's all I have :) anyway, since I'm not a windows guy, some of
this might be common knowledge, but I
It's currently at:
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/home.htm
although MS seem to change most of their links every week ;)
ugh. I found that but wasn't using msie so the js errors kept be from
seeing the dropdowns.
I don't think you need the Platform SDK
I hate even including the links as they are staled often.
yeah.
but here's a patch anyway that at least matches my recent experience. if it
looks ok to the people that use the platform regularly I'll hand it over to
httpd-docs.
--Geoff
blarg. patch attached
Geoffrey Young wrote:
I hate even including the links as they are staled often.
yeah.
but here's a patch anyway that at least matches my recent experience. if it
looks ok to the people that use the platform regularly I'll hand it over to
httpd-docs.
--Geoff
Jess Holle wrote:
My apologies if this is better done on the user group, but I've been
reading Apache source code and trying to understand the following.
Is there any way to signal mod_deflate that a particular response should
not be deflated when:
1. the URL of the request is
Jim Jagielski wrote:
There are a few open patches floating about, but in general I think
we're close to a point where we should seriously consider 1.3.30.
I volunteer to be RM... I'd like to shoot for mid-late next
week for a release.
Comments?
I just added a simple thing to STATUS that
hi all...
the MSIE + query string and mod_auth_digest came up again yesterday in
bugzilla:
http://issues.apache.org/bugzilla/show_bug.cgi?id=27758
the issue was discussed here a while ago, most notably in
http://marc.theaimsgroup.com/?t=10551086801r=1w=2
with most people thinking
Paul Querna wrote:
On Fri, 2004-03-19 at 16:59, Geoffrey Young wrote:
it probably needs a better name, though :)
AuthDigestEnableQueryStringHack is a great name.
Its an fugly name for an fugly Hack. I forget who originally suggested
the name, but I like it.
ok :)
Geoff, I like
André Malo wrote:
* apache [EMAIL PROTECTED] wrote:
location !~ regex or location -v regex would be very nice
in certain case for exemple, enable client certificat auth for the entire
site but 2 locations
LocationMatch ^(?!non-location1|non-location2)
should do (in 2.x).
I played
Geoff, I like your approach in that patch. It keeps that huge if() from
getting any bigger or more complicated.
cool. I'll give it a few more days to marinate, but if nobody complains or
has a better implementation suggestion I'll check it in around tuesday of
next week.
committed to
But with the right combination of modules, it is very easy to see that
when a module calls ap_custom_response() on some flow, subsequent
requests with no such call will still get the previously-registered
response string.
While I have not hit crashes myself in testing
over in perl-land I
hi all
in 2.1 there is no supported API for a digest provider to deny a user
outright before a password match is tried.
digest providers are currently limited to AUTH_USER_NOT_FOUND or
AUTH_GENERAL_ERROR for errors. recent changes in AUTH_GENERAL_ERROR make it
return 500 to match how Basic auth
Justin Erenkrantz wrote:
--On Monday, April 5, 2004 9:35 AM -0400 Geoffrey Young
[EMAIL PROTECTED] wrote:
releases control to the next provider in the chain. this all leaves
digest
providers without a way to return 401 and stop the authentication chain.
basic providers, however, can use
hi all
today in bugzilla Joshua brought up an interesting point about ErrorDocument
- once set on a global or per-server level you can't selectively restore the
error response back to the canned server document.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28173
while the current
Cliff Woolley wrote:
On Mon, 5 Apr 2004, Geoffrey Young wrote:
ErrorDocument 500 default
in core httpd, allowing users to effectively restore the canned server
response for the scope of the current ErrorDocument.
anyway, I'm just tossing the idea out there - if people like it I'll work
[EMAIL PROTECTED] wrote:
geoff 2004/04/08 17:56:26
Modified:.CHANGES
server core.c
Log:
Enable special ErrorDocument value 'default' which restores the
canned server response for the scope of the directive.
if this stays in 2.1 it will need
Just edit the .xml. (There is a big ugly note at the top of the .html.en
telling you not to touch it.) Then you can build the .html.en using
the instructions here:
http://httpd.apache.org/docs-project/docsformat.html
Or if you don't want to bother, just do the .xml and someone else will
[EMAIL PROTECTED] wrote:
nd 2004/04/10 11:40:53
Modified:server core.c
Log:
ErrorDocument default changes broke inheritance. consider:
Directory /foo
ErrorDocument 404 blah
/Directory
DIrectory /foo/bar
ErrorDocument 500 boo
# 404 is now fallen
Joshua Slive wrote:
I do have one question about this: Is anyone actually using mod_digest?
I was under the impression that there doesn't exist any client that can
interoperate with this module (as opposed to mod_auth_digest, which
supports modern clients). If this is true, why don't we
Craig Sebenik wrote:
It looks like mod_ext_filter sets the last-modified http header based on
the mod time of the *filter* file and not the actual file represented by
the URL.
the Last-Modified HTTP header seems to be set based on the timestamp on
/web_home/filters/filter.pl and NOT on
+(December 2003), most major browsers support digest
+authentication. However, the only major browsers which support
+the old digest authentication format are a
href=http://www.opera.com/;Opera 4.0/a,
+a href=http://www.microsoft.com/windows/ie/;MS Internet
+
Use of uninitialized value in concatenation (.) or string at
/home/sctemme/asf/perl-framework/Apache-Test/lib/Apache/TestRequest.pm
The single request for /index.html is the framework's ping to see if
the server has started. It is not part of the errordoc tests, which
suggests that
cross-posting to test-dev@, which is probably where we ought to discuss the
gory details...
Failed Test Stat Wstat Total Fail Failed List of Failed
at this point the test part of the perl-framework is
Jim Jagielski wrote:
I plan to TR 1.3.31 most likely tomorrow... speak now
or forever hold your peace.
I don't think the mod_digest.html stuff I sent was integrated, even though
it seemed people were happy with the wording. but I didn't want to just
commit it until the RM officially said so
Sumeet Singh wrote:
Brian,
If you ask me, I can write the new functions (i.e. the apr_table_do -
type functions you described) and submit a patch for review. Let me know
I have often wanted an apr_table_do-esque interface that allowed for
modification of table entries as suggested, so
I put the new version at http://apache.org/~sctemme/mod_example_ipc.c
to save on e-mail bandwidth.
if you're interested in this kind of thing, I've wrapped up mod_example_ipc
in an Apache-Test tarball:
http://perl.apache.org/~geoff/mod_example-ipc.tar.gz
for no particular reason except
FYI, Fitz did a conversion of apache-1.3, which is now located at
http://svn.apache.org/repos/test/httpd/. (in the test repository).
wow, that's a lot of data - 10 minutes later and I'm still downloading...
I guess it goes without saying that most of the people here are intimate
with svn.
This is going to be a recurring problem. Geoff did the intuitive
thing, which turned out to be wrong. Not good.
Documentation issue... IMO, Sander should have added a note to his
conversion notice about how to checkout the trunk of the repository.
yeah, I'd agree with this - including
hi all
I wanted to ping everyone about an idea I've been throwing around for a few
months now. I'd like the ability to shuffle the declared hook ordering
around, most likely during the post-config phase.
basically what I would like to be able to do is shift a hook from one place
(say,
Cliff Woolley wrote:
On Wed, 9 Jun 2004, Geoffrey Young wrote:
I wanted to ping everyone about an idea I've been throwing around for a few
months now. I'd like the ability to shuffle the declared hook ordering
around, most likely during the post-config phase.
There was some discussion
Cliff Woolley wrote:
On Wed, 9 Jun 2004, Geoffrey Young wrote:
I wanted to ping everyone about an idea I've been throwing around for a few
months now. I'd like the ability to shuffle the declared hook ordering
around, most likely during the post-config phase.
There was some discussion
Philippe M. Chiasson wrote:
The only moment where it's appropriate for a module to push Defines
values into
ap_server_config_defines is during the register_hook phase. The problem
is that
this phase is called earlier for compiled-in modules than for loaded
modules.
So a module trying to
hi all...
any feedback on this? the original patch is here:
http://marc.theaimsgroup.com/?l=apache-httpd-devm=108693011011443w=2
--Geoff
ok, here's a first pass at just a small part - achieve the hook listing by
offering an apr_table_do()-esque iterator just for hooks.
the output of
Sander Striker wrote:
Hi,
My second attempt at preparing a 2.0.50 rc tarball...
I've tagged the tree (STRIKER_2_0_50_RC2) and uploaded associated
tarballs to:
http://httpd.apache.org/dev/dist/
Please test and report.
plays nice with mod_perl-2.0 on fedora core 1. also plays
Tom Alsberg wrote:
On Tue, Jun 22, 2004 at 10:09:39PM +0200, Sander Striker wrote:
Hi,
My second attempt at preparing a 2.0.50 rc tarball...
OK, I'll be more direct now (my last mail to this list has apparently
been ignored). Can you please try to get this:
[EMAIL PROTECTED] wrote:
martin 2004/06/29 07:08:17
Modified:server main.c
Log:
Add OS and APACHE_MPM_DIR to -V output
just FYI, APACHE_MPM_DIR was removed in favor of naming the specific MPM in
-V ouput. see
hi all...
can somebody just take a quick look at this backport patch to verify that
I'm doing the minor bump properly?
thanks
--Geoff
Index: CHANGES
===
RCS file: /home/cvs/httpd-2.0/CHANGES,v
retrieving revision 1.988.2.310
diff
hi all...
the bug reporting skeleton has become so useful for me (and others) that I
have created two new skeletons:
http://perl.apache.org/~geoff/Apache-Test-skeleton-mp1.tar.gz
http://perl.apache.org/~geoff/Apache-Test-skeleton-mp2.tar.gz
these are essentially the same as the bug
Which in turn means that every filter, now blissfully unaware of ranges,
is forced to generate a full response for each byterange request. In the
case of a downloaded ISO (for example), this means a significant amount
of data (many hundreds of MB) is being processed by filters on each
[EMAIL PROTECTED] wrote:
pquerna 2004/07/10 00:47:23
Modified:.Tag: APACHE_2_0_BRANCH CHANGES STATUS
modules/aaa Tag: APACHE_2_0_BRANCH mod_auth_digest.c
Log:
Backport of AuthDigestEnableQueryStringHack
Needs a doc update to explain what it does.
Graham Leggett wrote:
Geoffrey Young wrote:
while I'm all for reducing server overhead (who isn't :) playing these
kind
of games with the filter API seems like such a bad idea. what we have
now
is a modular design that is simple and works - content handlers
generate a
response, while
Graham Leggett wrote:
Geoffrey Young wrote:
please take the rest of this as just a friendly discussion - I don't
want it
to turn into some kind of bickering match, since that's definitely not
what
I have in mind :)
Cool no problem - it's quite a complex thing this, and I
Does it have sence or there is another standrd way (without introducing
addtional hooks) to use standard authentication modules with access control
modifing at runtime?
I would look into the Satisfy directive, specifically whether Satisfy any
could be used in conjunction with core access
hi all
I was just in garrett's APR talk here at oscon and he was mentioning the
APR_STATUS_IS_SUCCESS macro, which I found interesting since httpd only uses
it in a few places, opting for a direct comparison to APR_SUCCESS instead.
should we move to APR_STATUS_IS_SUCCESS in all places? can
cross-posted to [EMAIL PROTECTED]
Garrett Rooney wrote:
Geoffrey Young wrote:
hi all
I was just in garrett's APR talk here at oscon and he was mentioning the
APR_STATUS_IS_SUCCESS macro, which I found interesting since httpd
only uses
it in a few places, opting for a direct comparison
Dan Wilga wrote:
The information contained in the access log can be quite useful in
tracking down problems. However, because the log entry is created only
after all output has been sent to the client, there is a problem I
sometimes run into:
If the child process creating the output (like
hmm, I guess this fell off the collective radar.
any comments? otherwise, I guess it's good enough and I'll just commit it
to both 2.0 and 2.1.
--Geoff
Geoffrey Young wrote:
[EMAIL PROTECTED] wrote:
pquerna 2004/07/10 00:47:23
Modified:.Tag: APACHE_2_0_BRANCH CHANGES
1 - 100 of 454 matches
Mail list logo
