mod_proxy + mod_cache problem, loosing EOS bucket

Hi, i'am working on mod_cache and mod_mem_cache + mod_proxy i found a problem with EOS Bucket. mod_cache is inserting his cache_in filter in output_filter when he wants to insert data in the cache. when mod_cache is used with mod_proxy, the cache_in filter is called after mod_proxy call

Re: cvs commit: httpd-2.0/docs/manual/platform ebcdic.xml index.xml ebcdic.html.en index.html.en

Joshua Slive [EMAIL PROTECTED] writes: Jeff Trawick wrote: There probably does need to be an EBCDIC section describing minor issues with the core code and with standard modules (e.g., SSI files need to be in the native character set so that mod_include can parse them*). Anyone feel

Re: mod_proxy + mod_cache problem, loosing EOS bucket

Hi again, the problem seems to be in the proxy. When proxy read the data and pass it to output filter, it do: while (ap_get_brigade){ ap_pass_brigade(output_filter) } si if the data aren't read by only one brigade, the mod_cache can't work. because it will try to cache only the first

Re: [VOTE]: Where to place I/O logging

Bojan Smojver [EMAIL PROTECTED] writes: Just so that I can put this one to rest (i.e. prepare the final patch accordingly), could you please vote: [ ] Put I/O logging on mod_log_config and have LogInputOutput flag [ ] Put I/O logging in a separate module, mod_logio The logic you're

Patch mod_proxy: mod_proxy + mod_cache problem

Hi again :) I did a patch modifiying mod_proxy to pass the entire data (response from backend server) to output_filter, unstead of brigade per brigade. it seems to work well... Matthieu Matthieu Estrade wrote: Hi again, the problem seems to be in the proxy. When proxy read the data

RE: Patch mod_proxy: mod_proxy + mod_cache problem

Hi again :) I did a patch modifiying mod_proxy to pass the entire data (response from backend server) to output_filter, unstead of brigade per brigade. One comment (having not reviewed the patch): Proxy should stream bytes from the backend server to the client as those bytes arrive. Proxy

Re: [VOTE]: Where to place I/O logging

On Mon, 2002-09-23 at 22:20, Jeff Trawick wrote: Bojan Smojver [EMAIL PROTECTED] writes: Just so that I can put this one to rest (i.e. prepare the final patch accordingly), could you please vote: [ ] Put I/O logging on mod_log_config and have LogInputOutput flag [ ] Put I/O logging

Re: Patch mod_proxy: mod_proxy + mod_cache problem

Matthieu Estrade wrote: I did a patch modifiying mod_proxy to pass the entire data (response from backend server) to output_filter, unstead of brigade per brigade. AFAIK the problem stems from a limitation in mod_cache where it can only cache stuff in a single brigade at the moment. Proxy

Re: [VOTE]: Where to place I/O logging

Jeff Trawick wrote: Bojan Smojver [EMAIL PROTECTED] writes: Just so that I can put this one to rest (i.e. prepare the final patch accordingly), could you please vote: [ ] Put I/O logging on mod_log_config and have LogInputOutput flag [ ] Put I/O logging in a separate module, mod_logio

Re: Patch mod_proxy: mod_proxy + mod_cache problem

hi bill, I agree with you about the proxy... Do you think it's possible to force the cache filter, be runned after all the proxy filters ? Matthieu Bill Stoddard wrote: Hi again :) I did a patch modifiying mod_proxy to pass the entire data (response from backend server) to output_filter,

graceful?

Has anybody torture tested graceful restarts lately? I only ask because we just got a PR that gave me that sinking feeling. Maybe not a real problem, but just figured I'd ask. --Cliff

Re: graceful?

Cliff Woolley wrote: Has anybody torture tested graceful restarts lately? I only ask because we just got a PR that gave me that sinking feeling. Maybe not a real problem, but just figured I'd ask. Not me lately... What's the # ? --

Re: Patch mod_proxy: mod_proxy + mod_cache problem

Matthieu Estrade wrote: I agree with you about the proxy... Do you think it's possible to force the cache filter, be runned after all the proxy filters ? The cache filter is supposed to run after all the filters for maximum caching advantage. Regards, Graham --

Re: [VOTE]: Where to place I/O logging

On Tue, 2002-09-24 at 00:08, Ian Holsman wrote: This is why I want it in it's own module so people who don't want this information won't have to suffer the penalty And that's what my last patch is all about :-) Bojan PS. Plus, it's disabled by default :-))

Re: Patch mod_proxy: mod_proxy + mod_cache problem

Hi graham, the problem is the filter is called between two ap_pass_brigade by the reverse proxy... like: proxy: get_brigade (data from backend) pass_brigade(pass data to outputfilter) cache_filter get_brigade(data from backend) pass_brigade(pass_data_to outputfilter) on one response by the

Re: graceful?

Cliff Woolley wrote: On Mon, 23 Sep 2002, Jim Jagielski wrote: Not me lately... What's the # ? Oy... um, the last one? ;-] goes to look http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12033 Oh, and not to startle the 1.3.27 RM... I should have mentioned it's a 2.0 PR. =]

Re: Patch mod_proxy: mod_proxy + mod_cache problem

Actually, the problem is in the fact that there is more than one brigade and the cache code can't currently handle that. Proxy is working the way it is supposed to. This allows Apache to process large responses without having to buffer the whole thing inside Apache. Apache uses less memory, and

Re: Patch mod_proxy: mod_proxy + mod_cache problem

Graham Leggett wrote: Matthieu Estrade wrote: I agree with you about the proxy... Do you think it's possible to force the cache filter, be runned after all the proxy filters ? The cache filter is supposed to run after all the filters for maximum caching advantage. I disagree on

Re: Patch mod_proxy: mod_proxy + mod_cache problem

Hi Paul, I know about mod_cache is only working on one brigade, but my problem is not here. My problem is i can't setup the filter cache_in_filter to be executed after mod_proxy pass his last brigade to the filter chain Actually, mod_cache_filter_in is executed only one time when mod_proxy

Re: Releasing 2.0.42

[EMAIL PROTECTED] wrote: Sander Striker wrote: Hi, Done enough testing to say: +1 for GA I reserve my judgement until it has run longer without problems on daedalus. I'm now confident that 2.0.42 is stable. Greg

Re: graceful?

Cliff Woolley wrote: Has anybody torture tested graceful restarts lately? I only ask because we just got a PR that gave me that sinking feeling. Maybe not a real problem, but just figured I'd ask. They work on daedalus with prefork. But that's typically just once a night - not sure if

APXS

From the code in apxs; when one does an apxs -ia mod_foobar.so I get the error from below. Which can be easily fixed by using the -n flag as advised. Now naively this seems to be because by '1' we eat too much from the back of the string (i.e. the full '.so') while we expect something

2.0 mod_dav thinks / isn't a collection, mod_dir gets in the way

I've switched my home server from a Linux box running httpd 1.3 to my Mac running httpd 2.0. For my each site I host, I've got two virtual hosts, one which is the public server and another which is DAV-enabled for editing. I usually just mount the DAV server using the DAV filesystem in

RE: Releasing 2.0.42

Just as a matter of interest, which version or what date did the APR/APU snapshot come from? I recently made some changes to APR for SCO OpenServer that'd be great if they went out with 2.0.42. Kean. I'm now confident that 2.0.42 is stable.