mod_log_config cookie buglet

hi all :) a co-worker and I were just adding some functionality to an internal httpd module when we noticed that mod_log_config misbehaves when logging cookie values... in short, we have a cookie FOO and were adding a cookie CLIENT_FOO. in the log format we used %{FOO}C\t%{CLIENT_FOO}C but t

set_define() warnings

hi all :) the new set_define() function currently has some unused variables, so it won't compile with -Werror patch attached. --Geoff Index: server/core.c === --- server/core.c (revision 549098) +++ server/core.c (working copy) @@ -

Re: [RELEASE CANDIDATE]: Apache-Test-1.29-RC3

Steve Hay wrote: > Philip M. Gollucci wrote: > >> A release candidate for Apache-Test 1.29-rc3 is now available. >> >> http://people.apache.org/~pgollucci/at/Apache-Test-1.29-rc3.tar.gz looks good on apache 2.2.2, perl 5.8.8 +1 --Geoff

Re: Custom Listen statement in perl-framework (Was: Re: [VOTE] 2.2.2 Candidate)

resending to all the interested lists... Sander Temme wrote: > > On Apr 23, 2006, at 9:37 AM, Paul Querna wrote: > >> Sander Temme wrote: >> >>> FreeBSD bagheera.sandla.org. 6.1-RC FreeBSD 6.1-RC #3: Fri Apr 21 >>> 08:35:33 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/ >>> src/sys/GENERIC i386

Re: Custom Listen statement in perl-framework (Was: Re: [VOTE] 2.2.2 Candidate)

Sander Temme wrote: > > On Apr 23, 2006, at 9:37 AM, Paul Querna wrote: > >> Sander Temme wrote: >> >>> FreeBSD bagheera.sandla.org. 6.1-RC FreeBSD 6.1-RC #3: Fri Apr 21 >>> 08:35:33 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/ >>> src/sys/GENERIC i386 >>> Testsuite currently unusable, hangs

[ANNOUNCE] Apache-Test 1.28

mod_imap or mod_imagemap [ Colm MacCarthaigh ] shortcuts like need_cgi() and need_php() no longer spit out bogus skip messages [Geoffrey Young] Adjust Apache::TestConfig::untaint_path() to handle relative paths that don't start with /. [Stas] If perlpath is longer than 62 chars, some shel

Re: [RT] what's the roadmap?

> I think that's a good idea, so long as [EMAIL PROTECTED] > can withstand the occasional question about our > perl glue. Someday I'd actually like to see > trunk/glue/perl moved over to mod_perl's trunk, > and our C code folded into httpd somehow, but > that may take some time doing. in princi

Re: perl-framework, Makefile.PL with -apxs gives error.

> 2. perl Makefile.PL > -apxs /home/sris/projects/ers-3-0-2/apache2.0/bin/apxs > 3. make > 4. t/TEST > > > OUTPUT > > [EMAIL PROTECTED]:~/projects/temp/httpd-test/perl-framework$ t/TEST > [warning] setting ulimit to allow core files > ulimit -c > unlimited; /usr/bin/perl > /home/sris/projects

Re: [RELEASE CANDIDATE] Apache-Test 1.28

Mark Galbreath wrote: > I'm drawing a blank for those following only dev@httpd.apache.org, and thus may be unaware of what Apache-Test is, here's the deal... Apache-Test http://perl.apache.org/Apache-Test/ is the engine that drives the perl-framework http://svn.apache.org/viewcvs.cgi

[RELEASE CANDIDATE] Apache-Test 1.28

check for mod_imap or mod_imagemap [ Colm MacCarthaigh ] shortcuts like need_cgi() and need_php() no longer spit out bogus skip messages [Geoffrey Young] Adjust Apache::TestConfig::untaint_path() to handle relative paths that don't start with /. [Stas] If perlpath is longer than 62 chars, s

Re: [proposal] remove [EMAIL PROTECTED]

Justin Erenkrantz wrote: > On Fri, Dec 16, 2005 at 12:04:56AM -0800, Justin Erenkrantz wrote: > >>I'd like to propose shutting down [EMAIL PROTECTED] and move it all back under >>[EMAIL PROTECTED] >> >>The traffic on [EMAIL PROTECTED] list doesn't justify a separate list, and the >>Apache-Test c

Re: [proposal] remove [EMAIL PROTECTED]

Justin Erenkrantz wrote: > I'd like to propose shutting down [EMAIL PROTECTED] and move it all back under > [EMAIL PROTECTED] > > The traffic on [EMAIL PROTECTED] list doesn't justify a separate list, and the > Apache-Test code is now property of the Apache::Perl PMC, so discussions of > that ar

Re: Authz refactoring discussion

Justin Erenkrantz wrote: > --On December 6, 2005 11:04:13 AM -0700 Brad Nicholes > <[EMAIL PROTECTED]> wrote: > >> Good, then I am +1 on the authz providers only returning AUTHZ_GRANTED >> or AUTHZ_DENIED. I don't see a need for anything else. > > > FWIW, I do see a case for returning 'uh-oh,

Re: proposed authz rewrite (was:Re: Suggest renaming mod_authz_host to mod_access_host)

>>or wathever. Killing AuthtType is good in that it propably lets you >>combine different Accesses with Auth much cleaner. >> >>Dw > > > Good point. After thinking about it, it seems that AuthType could be > eliminated completely. The authentication type is already implied by > the use of the

Re: mod_access vs mod_authz_host

Justin Erenkrantz wrote: > --On November 3, 2005 4:54:08 PM + Nick Kew <[EMAIL PROTECTED]> wrote: > >> Just to elaborate on that, it's the name I'm not happy about. >> I'm perfectly happy with the /modules/aaa/ classification. > > > The problem is that mod_access does not indicate the purp

Re: mod_access vs mod_authz_host

Nick Kew wrote: > On Thursday 03 November 2005 16:37, Brad Nicholes wrote: > >> But it does handle access control which kind of puts in the category >>of authz vs. anywhere else. > > > So can mod_rewrite and others, but that doesn't make it mod_authz_url! > Perhaps mod_load_average should be

Re: Missing Features of htdigest.c

Dirk-Willem van Gulik wrote: > On Mon, 25 Jul 2005, Eli Marmor wrote: > > >>3. A C program may be integrated into the source tree of Apache (or > > > And while gradually disappearing -I still see a lot systems in the field > which do not have perl installed or managed (as well) with apache.

Re: Missing Features of htdigest.c

> Well, maybe I explained it bad, so I'll try again: ok :) > > In 2.1, the AAA was totally restructured, to separate the algorithm > (BASIC or DIGEST or whatever) from the storage (FILE or DBM or a > database), and to open the full matrix of options to users. > > However, even if it was done i

Re: Missing Features of htdigest.c

> As I wrote in my previous message, for example, the only way to add a > user or change a password from a program and non-interactively, is by > hacking with TIOCNOTTY and then piping the password twice into > htpasswd. only? you can certainly add a new user via use Digest::MD5; my $user

Re: Apache::Test v1.25 error - Can't use string ("Test::Builder") as a HASH ref

Geoffrey Young wrote: >>Now, this looks like a bug. The T::B->reset method expects an object, >>Apache::Test calls it as a class method. I allow for the possibility that >>I've completely misunderstood everything--or even just some things. > > > well, it&

Re: [VOTE] mod_ftp for HTTP Server Project

Jim Jagielski wrote: > Now that Covalent has released it's ERS 3.0 distribution, mod_ftp is now > officially offered for donation/incubation/graduation to the ASF. sounds like fun > The entire code-base, including Perl test scripts for inclusion in > httpd-test, > is available and ready for do

Re: Multiple AAA providers

> AUTH_USER_NOT_FOUND acts as AUTH_DECLINED. > > The auth modules loop until it runs out of providers or it receives something > other than AUTH_USER_NOT_FOUND. -- justin duh. I saw that but was reading the logic wrong. thanks :) --Geoff

Re: Multiple AAA providers

> To fill out the example of the "Auth" container to better illustrate what > I mean, you might have this: > > > require ldap-group cn=Accounting,ou=Groups,ou=XXX > AuthLDAPBindDN cn=Mail,dc=XXX > AuthLDAPBindPassword blah1 > LDAPTrustedMode SSL > AuthLDAPURL ldaps://xxx.co.za/dc=xxx,d

Re: Multiple AAA providers

> This solves the problem for multiple providers, but the problem isn't > solved for where the same provider is used twice, for example: > > - If user is present in file A or file B > - If user is present in directory A or directory B hmm... isn't this kind of thing really up to the provider it

Re: Multiple AAA providers

> This functionality would be useful for more than just LDAP: you might want > to use two different flat file databases, or maybe you want to auth > someone in LDAP and someone else in SQL. > > This is really an AAA-wide question rather than an LDAP specific question. > > Anyone know how difficu

Re: Actively Promoting Apache 2

Paul Querna wrote: > Ian Holsman wrote: > >> Also I would start discussing with some of the other 1.3-only module >> writers out there on how to port their stuff to 2.0, or port it for them. > > > There are not many left now Just those mod_perl guys, and they are > at 1.99.9. I think

Re: [PATCH] tracking active request phase

Jeff Trawick wrote: > On Mon, 28 Feb 2005 08:39:06 -0600, William A. Rowe, Jr. > <[EMAIL PROTECTED]> wrote: > >>Wow :) That would be extraordinarily useful. Any hope the scheme >>would be extensible, so a module such as cgi or rewrite could show >>more specific Phases? > > > I'm leaning towa

Re: The use of CORE_PRIVATE

Bojan Smojver wrote: > "if I rely on what's below CORE_PRIVATE, am I setting myself up > for a disaster when those things change without notice?" I think the answer to this is similar to the old line "if you need to ask how much it costs you can't afford it." ;) --Geoff

Re: Apache-Test subdirectory has moved

> Also Geoff please don't forget to update the documentation. Both inside > the module and at perl.apache.org docs. Thanks. I couldn't find any mentions of the location of the repository outside of README-SVN. do you know of others? additionally, we should probably update httpd.apache.org/test

Re: [PATCH] set username from certificates at a more appropriate time

Joe Orton wrote: > I presume this fixes #31418? Your patch makes sense to me. I could > argue that it could even be done *before* the SSLRequire checking, such > that the "username" is logged appropriately even if an SSLRequire > triggers a 403, but I doubt that matters much. fwiw that's the r

Re: FakeBasicAuth - a howto anywhere?

>>I made the change, and it now works, thanks! >> >>Is it possible to fix mod_authn_anon? How hard is the bug to fix? > > > Not that hard. If nobody beats me, I'm going to make it over the weekend. > It's because conf->anyuserid is not checked in the provider when no further > user id is configu

Re: How to change ap_document_root variable from a apache2 module ?

>>>This can be done quite safely in Apache1, by the way. >> >>I don't believe it can. Code? > > > Well, since you don't need to worry about thread safety as long as you set > it on every request, or reset it after each request you are fine. > Something like: > > foo->old = ap_document_root(r)

Re: Apache and Application driven Basic Auth

ok, it just hit me that my last response was probably too academic for your needs. this part escaped me... > Apache does all that but only against its files, not against application > generated requests. > Anyway if I do this inside of my tag: > All requests are going through and my Auth requ

Re: Apache and Application driven Basic Auth

> I'm trying to understand whether Apache even supports application driven > Basic Authentication. it does, but our ideas of "application" are very different. more on that later... > It seems odd that this should be difficult to do - > I've worked with a fair number of Web Servers over the yae

Re: Apache and Application driven Basic Auth

Rick Strahl wrote: > Thanks Geoff, > > >>I think you need a Require directive > > > Yes I do ... but as soon as I put a Require in there it tries to validate > every request into the directory. yes it does :) > This is not what's requried. > > I need conditional authentication that's gener

Re: Apache and Application driven Basic Auth

> AuthType Basic > AuthUserFile d:\server\users\passwords.txt > Is there anything I'm missing here? I think you need a Require directive http://httpd.apache.org/docs/mod/core.html#require HTH --Geoff

Re: mod_ssl exported functions?

Torsten Foertsch wrote: > Hi, > > I am writing a mod_perl module that makes mod_ssl optional functions > accessible via perl. I have currently implemented ssl_is_https() and > ssl_var_lookup() which is enough for my needs. for the record, this interface is/was already available for perl on CP

Re: svn commit: r111386 - /httpd/httpd/trunk/CHANGES /httpd/httpd/trunk/include/httpd.h /httpd/httpd/trunk/modules/http/http_protocol.c

> I will veto it. -1. I consider 3229 to be harmful to HTTP and do not > wish to > support it in the current form. Folks can still implement it with > extensions > if needed. the change was backed out as r111432 --Geoff

Re: svn commit: r111386 - /httpd/httpd/trunk/CHANGES /httpd/httpd/trunk/include/httpd.h /httpd/httpd/trunk/modules/http/http_protocol.c

>> add response code 226 constant (HTTP_IM_USED) and status >> line ("226 IM Used"). PR 31128. > > > As I emailed when this patch and issue was originally opened, I thought > this patch was unnecessary. I'll pull it out if you want, but I thought it sounded like a decent enough idea and there

Re: Bug #31228

> Just a reminder to make sure this doesn't fall off the radar ;-) yeah, sorry about that. call it day job encroachment :) here's a patch against current HEAD (trunk?). I'll give it a day or two to marinate and commit before the week is out if there are no complaints. fwiw, the perl-framework

Re: mod_comment

>>but in that >>respect, we are no different from any other module that wants to implement a >>RAW_ARGS directive... > > > Hardly. RAW_ARGS takes a single line of text. No file pointer. That > line could come from anywhere. yeah, ok. I _meant_ create your own container, which I guess is the t

Re: mod_comment

Justin Erenkrantz wrote: > --On Monday, November 29, 2004 10:41 AM -0800 Greg Stein > <[EMAIL PROTECTED]> wrote: > >> but we were not allowed to remove features. Removing the fp from the >> API would have disabled this "feature" in mod_perl, among others. > > > I can't tell you how often I've

Re: Bug #31228

>>So, uhh, ping? Any comments other than "i'm iffy" and "is there any >>reason not to add it"? > > > +1 (concept; implementation not verified) here too. is this the most recent patch: http://issues.eu.apache.org/bugzilla/attachment.cgi?id=12746 ? if so, I'll try and review the implementa

Re: Whitespace strip filter for httpd v2.1

Graham Leggett wrote: > Hi all, > > I have attached a small filter module that strips leading whitespace > from text files. This would typically be used to remove the "indenting" > whitespace found inside HTML files, resulting in a significant reduction > in network traffic for some sites. > >

Re: ErrorHeader directive and CHANGES

> In this case, I think, no. It's clearly stated in 2.0, that's a backport from > the development branch (since it were different changes to the code base). ok. it still feels a little strange to talk about something that was both (re)added and removed between releases, since the net change is n

ErrorHeader directive and CHANGES

hi all... we have the following entries in CHANGES under 2.1-dev: *) Drop the ErrorHeader directive which turned out to be a misnomer. Instead there's a new optional flag for the Header directive ('always'), which keeps the former ErrorHeader functionality. [André Malo] *) mod

Re: [NOTICE] Subversion conversion

> It's just that someone needs to simultaneously move modperl-2.0 to > subversion too. And modperl-docs too, since they are checked out into > modperl-2.0 check out. As long as this is all done at once there should > be no problem. None of these projects had any branching so it shouldn't > be a pr

Re: [NOTICE] Subversion conversion

Sander Striker wrote: > Hi, > > I'm finally taking care of the conversion of httpd-* to SVN. > I'll follow up with instructions on how to pull new workingcopies, > etc etc. I'm looking for volunteers to actually write a page > for developers on where to get SVN and how to check out the > source

Re: Use threaded MPM by default was Re: cvs commit: httpd-2.0 STATUS

> Seems reasonable to do so. 2.0 was our first threaded release - making > a threaded MPM by default (if available) for 2.2 seems fine by me. -- > justin agreed :) however, something that I heard recently is that if you specify a threaded MPM on a platform that does not support it, the build p

Re: cvs commit: httpd-2.0/modules/mappers mod_rewrite.c

> (though with proxy > issues on HEAD mod_rewrite [P] stuff is still completely broken). yeah. if I have the time I'll try to track down exactly the revision that caused this failure so it can also be added to showstoppers, if merely so somebody takes the time to explicitly address it. not sur

Re: [RFC] Patch for mod_log_config to allow conditioning on status code

>For a start I'd like to invite comments on a) the concept and b) the > syntax. this sounds interesting in general, although I find myself wondering about a different approach - expanding SetEnvIf to include response-type things (like status, content-type, etc) in addition to request-type thi

Re: mod_proxy broke RewriteRule ... [P]

just in case this fell through the cracks, does anyone have any ideas? --Geoff Joe Orton wrote: > Noticed first in the mod_perl tests, but this is an equivalent repro > case. mod_proxy in HEAD no longer allows modules to set r->handler = > "proxy-server" and force a request to be proxied (when P

Re: cvs commit: httpd-2.0/modules/mappers mod_rewrite.c

[EMAIL PROTECTED] wrote: > trawick 2004/09/18 09:18:27 > > Modified:.CHANGES >modules/mappers mod_rewrite.c > Log: > mod_rewrite: Handle per-location rules when r->filename is unset. > Previously this would segfault or simply not match as expected, > dep

Re: Bug #31228

Garrett Rooney wrote: > Justin Erenkrantz wrote: > >> --On Friday, September 17, 2004 1:07 PM -0400 Garrett Rooney >> <[EMAIL PROTECTED]> wrote: >> >>> Could someone please take a look at bug 31228 in bugzilla? >>> >>> It's just adding a new response code (226) which is defined in rfc3229. >>> >

Re: Moving httpd-2.0 to Subversion

Paul Querna wrote: > The Original Proposal was in March of this year: > http://marc.theaimsgroup.com/?t=10791831443&r=2&w=2 > > +1 Votes: > Tom May > Justin Erenkrantz > Andrà Malo > Erik Abele > Jim Jagielski > Bill Stoddard > Joe Orton +1 here, too. --Geoff

Re: [PATCH] don't crash with per-dir (location) rewrite config and NULL r->filename

> I'm afraid I don't understand. yeah, I'm sorry, that's my fault :) I should have taken the time to analyze the code in context and follow it all through. having done that, the only thing that comes to mind is I wonder how much logic can be skipped if r->filename is NULL and you assign it r->u

Re: [PATCH] don't crash with per-dir (location) rewrite config and NULL r->filename

>>odd to me that rewrite's translate_name hook, used for processing >>server config directives, can update r->filename permanently even when >>it declines > > > that's a common idiom for we mod_perl people :) actually, I take that back (not enough coffee yet) - we do that with r->uri (like ever

Re: [PATCH] don't crash with per-dir (location) rewrite config and NULL r->filename

Jeff Trawick wrote: > See attached patch. Given a module with map-to-storage hook which > leaves r->filename NULL, and config like the following, you get > segfault on platforms that don't like strlen(NULL). given that, I understand this part -if (strcmp(r->filename, ofilename) ==

Re: Time for 1.3.32 ?

André Malo wrote: > * Jim Jagielski <[EMAIL PROTECTED]> wrote: > > >>In general, people don't look for 1.3 patches in the 2.0 STATUS file >>and vice-versa :) > > > As far as I can see, the current way to make changes is 2.1 -> 2.0 -> 1.3. > So it makes sense for me to look into 2.0 for possib

[PATCH] backport static module checking in mod_so to 1.3

hi all. in 2.0 mod_so checks a given LoadModule statement against both static modules and those previously loaded by LoadModule. in 1.3 it checks only against those loaded with LoadModule, leaving open the possibility that someone will try to dynamically load a module that is already compiled int

Re: 2.1.0-rc1 tarballs up for testing

> Huh? > > % ./configure > checking for chosen layout... Apache > checking for working mkdir -p... yes > checking build system type... powerpc-apple-darwin7.5.0 > checking host system type... powerpc-apple-darwin7.5.0 > checking target system type... powerpc-apple-darwin7.5.0 > > Configuring Apa

Re: 2.1.0-rc1 tarballs up for testing

> I say something akin because just specifying > --with-apr=/foo/apr-1-config and --with-apu=/foo/apu-1-config isn't > sufficient for me to get it to compile (the config process is somehow > picking up an old /usr/include/apr-0 for me, despite my pointing to > ap(r|u)-1-config files in a fully-func

Re: 2.1.0-rc1 tarballs up for testing

> Note that the 2.1 tarball does _not_ come prepackaged with APR, you will > have to get the 1.0 version of apr and apr-util seperately at: > > http://apr.apache.org/download.cgi I certainly understand the reason for this. however, I can't find any documentation in the RC that notes the separ

Re: AddOutputFilterByType oddness

Graham Leggett wrote: > Nick Kew wrote: > >>> I have just set up the most recent httpd v2.0.51-dev tree, and have >>> configured a filter that strips leading whitespace from HTML: >>> >>> AddOutputFilterByType STRIP text/html >>> >>> The content is served by mod_proxy. > > >> As it stands, tha

Re: proxy compile warnings

> Adding it to mod_proxy.h is right the thing. > The idea is to have a ap_proxy_pre_request and ap_proxy_post_request: > one called before "processing" the request and one after. ok, cool. attached is a new patch that addresses this. sorry for the excess dialogue - this would have been obvious

Re: proxy compile warnings

William A. Rowe, Jr. wrote: > At 04:36 PM 8/17/2004, Joe Orton wrote: > >>On Tue, Aug 17, 2004 at 11:48:39AM -0400, Geoffrey Young wrote: >> >>>hi all >>> >>>the attached patch is required for me to get mod_proxy to compile with -Werror. >>

proxy compile warnings

hi all the attached patch is required for me to get mod_proxy to compile with -Werror. --Geoff Index: modules/proxy/proxy_ftp.c === RCS file: /home/cvs/httpd-2.0/modules/proxy/proxy_ftp.c,v retrieving revision 1.145 diff -u -r1.145 p

Re: httpd-2.2 release roadmap v0.1

> I really think the mod_auth stuff makes it so much easier to write > aaa backends, that we're doing a great disservice to our module writers > by holding back on 2.2 even by a single day. indeed :) so, can someone comment on what 2.2 (and the subsequent 2.3) mean for 2.0? that is, if every

Re: cvs commit: httpd-2.0/modules/aaa mod_auth_digest.c

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 >> >> Modifie

Re: Suggestion: log request when it happens

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 (

Re: using APR_STATUS_IS_SUCCESS

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 &

using APR_STATUS_IS_SUCCESS

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 someo

Re: question concerning with authentication process

> 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

Re: The Byterange filter -- a new design -- feel free to rip it to shreds

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 :) > >

Re: The Byterange filter -- a new design -- feel free to rip it to shreds

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 sim

Re: cvs commit: httpd-2.0/modules/aaa mod_auth_digest.c

[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 do

Re: The Byterange filter -- a new design -- feel free to rip it to shreds

> 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 > re

Apache-Test module skeletons

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 reporting

backport with minor bump

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 -u

Re: cvs commit: httpd-2.0/server main.c

[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 http://cvs.apache.org/viewcvs.cgi/httpd-2.0/server/main.c

Re: Apache HTTP Server 2.0.50-rc2 tarballs available for testing

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: > > http://issu

Re: Apache HTTP Server 2.0.50-rc2 tarballs available for testing

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

Re: Dumping Loaded Modules

Paul Querna wrote: > Attached is patch add a new command line option to httpd: > '-t -D DUMP_MODULES' > > This will print a list of all loaded shared modules and all statically > compiled modules. > > My only question is, what should the command be called? > > '-t -D DUMP_MODULES' vs '-M' vs s

Re: dynamic hook ordering

hi all... any feedback on this? the original patch is here: http://marc.theaimsgroup.com/?l=apache-httpd-dev&m=108693011011443&w=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

Re: [Patch] Prevent coredump when statically linked module tries to access ap_server_config_defines from register_hooks

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 tryin

Re: dynamic hook ordering

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

Re: dynamic hook ordering

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

dynamic hook ordering

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, HOOK_FIRST

Re: Move apache-1.3 to Subversion

>> 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 - inclu

Re: Move apache-1.3 to Subversion

> 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.

Re: Better error logging for mod_access

Joshua Slive wrote: > On Sat, 5 Jun 2004, Rici Lake wrote: > >>>What about keeping the old error message, but logging an *additional* >>>message at loglevel debug with the additional info? >> >>That is certainly possible but I was trying to make things as easy as possible >>for newbies. I think

Re: Apache 1.3.31 RC Tarballs available

> 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

Re: Apache 1.3.31 RC Tarballs available

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 lar

Re: Sample code for IPC in modules

> I put the new version at > 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

Re: [PATCH] RFC: Allow modification/deletion of specific headers in apr_table_t

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 t

Re: T&R of 1.3.31

Jim Jagielski wrote: > I plan to T&R 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

Re: cvs commit: httpd-docs-1.3/htdocs/manual/mod mod_digest.html

> +(December 2003), most major browsers support digest > +authentication. However, the only major browsers which support > +the old digest authentication format are href="http://www.opera.com/";>Opera 4.0, > +http://www.microsoft.com/windows/ie/";>MS Internet > +Expl

Re: mod_ext_filter and last-modified header

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 N

Re: [PATCH] Candidate 1: Re: 1.3.3x digest/nonce issue

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

Re: cvs commit: httpd-2.0/server core.c

[EMAIL PROTECTED] wrote: > nd 2004/04/10 11:40:53 > > Modified:server core.c > Log: > "ErrorDocument default" changes broke inheritance. consider: > > > ErrorDocument 404 blah > > > ErrorDocument 500 boo > # 404 is now fallen back to default > > > T

  1   2   >