Re: input filters with mod_ext_filter [patch]

Am Montag, 23. Juni 2003 19:02 schrieben Sie: On Mon, Jun 23, 2003 at 10:26:55AM +0200, Philipp Reisner wrote: Am Montag, 23. Juni 2003 03:56 schrieb Jeff Trawick: (apologies for missing the right mail reference and nasty quoting... e-mail problems, and luckily I was browsing the archives

Re: response handlers get all requests

[EMAIL PROTECTED] wrote: Marc M. Adkins wrote: The ap_hook_handler() call does not specify the handler key from the corresponding AddHandler configuration directive. As a consequence, the specified handler function must look at and accept or decline each request. yes, you are

headers for an input filter in AP_FTYPE_CONNECTION mode ?

Hi, Now since I can do input (request) filtering with mod_ext_filter, I tried to set ftype = AP_FTYPE_CONNECTION and expected to get the headers. If you set ftype to AP_FTYPE_CONNECTION on an output filter, it will get the complete response including headers. I have to add that I deployed my

RE: Module help...

Hey again !! Thanks for getting back in touch. I read through the code you have and I'm not sure it does exactly what I'm aiming for, although it is a great start. The caching section I have seen examples for and I'am sure it wouldn't be too much to get it going. I know it is a lot of extra code

Re: headers for an input filter in AP_FTYPE_CONNECTION mode ?

Philipp Reisner wrote: Now since I can do input (request) filtering with mod_ext_filter, I tried to set ftype = AP_FTYPE_CONNECTION and expected to get the headers. If you set ftype to AP_FTYPE_CONNECTION on an output filter, it will get the complete response including headers. On output, the

Re: [PATCH] mod_cache RFC compliance

Thomas, I'm working on getting a patch in to CVS. The answer to question 1 is that, depending on how it got added, the various values could be in either err_headers_out or headers_out. I'm adjusting your patch (plus the other header references) accordingly. Should be done, tested, and committed

Re: 1.3.28

Jim Jagielski wrote: OK, let's get 1.3.28 out the door. I'd like to hear some feedback on whether there is stuff people want to see in this release. I'd also like some feedback on some testing on the latest HEAD. It is likely that 1.3.28 will be out there for quite awhile, so let's get it out

Re: mod_cgi and free_proc_chain

Lothar ? wrote: does anyone know how to increase the time apache will wait before sending a SIGKILL to cgi-processes? (Or to change the kill-policy used with subprocesses?) problem background: I'm using BerkeleyDB from my perl-cgi-scripts, but I don't know how to close the database in case of

Re: 1.3.28

Looking to tag on Friday. -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ A society that will trade a little liberty for a little order will lose both and deserve neither

hello world example module...?

Would there be any interest in including example modules with the Apache source distribution? And/or could a complete example module be included in the documentation for developers? (Personally I'd prefer it be included in the source distribution...The web documentation has become quite out of

Re: hello world example module...?

Chris Knight wrote: Would there be any interest in including example modules with the Apache source distribution? modules/experimental/mod_example.c

Re[2]: [RELEASE CANDIDATE] Apache::Test 1.03-dev

Tuesday, June 24, 2003, 1:51:51 PM, you wrote: JS Rob Bloodgood [EMAIL PROTECTED] writes: JS [...] *** root mode: changing the fs ownership to 'nobody' (99:99) /usr/sbin/httpd -X -d /root/.cpan/build/Apache-Test-1.03/t -f /root/.cpan/build/Apache-Test-1.03/t/conf/httpd JS Is the docroot

Re: hello world example module...?

Jeff Trawick wrote: Chris Knight wrote: Would there be any interest in including example modules with the Apache source distribution? modules/experimental/mod_example.c Ah, fair enough. I wouldn't have thought of looking in experimental, however (I seemed to remember that there was an

ap_max_requests_per_child isn't part of the API, is it?

Some level of mod_php (presumably recent) won't load with Apache 2 on AIX, and the reason is that the decl of that variable in mpm_common.h isn't formally exported (AP_DECLARE_DATA). PHP should be using ap_mpm_query(), right? See http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21046

[PATCH] modify httpd.conf-dist defaults

Might be too late for 1.3.28, but I'd love some comments. - Changes defaults to disallow access to files unless explicitly allowed. - Turns off CGICommandArgs I haven't seen any scripts that still use this, but have come across more than a handful of scripts that were vulnerable. And this is

[PATCH] ErrorLogsWithVhost for Apache 1.3.28

This adds a directive ErrorLogsWithVhost that extends the error log format by adding server name and port to entries in the error logs. Proof of concept. Are there better ways to do this than using a global? Cheers, Glenn diff -ru apache_1.3.27/src/include/http_conf_globals.h

Re: [PATCH] modify httpd.conf-dist defaults

On Tue, 24 Jun 2003, Glenn wrote: Might be too late for 1.3.28, but I'd love some comments. - Changes defaults to disallow access to files unless explicitly allowed. Although this is, in general, a good idea, I think it would cause many people to be confused. I don't think it is a good idea

Apache thread creation?

I am new to apache modules and was wondering if its possible /allright to create new threads within a module during the module initialization?. I saw some api that allow child process creation and termination, but is there some equivalentfor threads as well? Thanks -Arvind Do you Yahoo!? SBC