On Mon, 05 Dec 2011 15:56:27 +0100 Dennis Jacobfeuerborn <dennisml@xxxxxxxxxxxx> wrote: > > Just out of interest shouldn't the FilterProtocol directive with cache=no > > have the same effect as the flag and if I set the flag in the code can I > > remove the directive from the configuration (once cache prevention is > > working as intended)? That's what I'm hoping to establish. We have a number of possibilities here: 1. A bug that affects both no-cache options. 2. A bug that affects the version you posted but not the one I'm suggesting. 3. Your report is missing something relevant, and consequently misleading. If (1) then I want to fix it, which means reproducing it first. If (3) then hopefully you'll get to the bottom of it, possibly with help. If (2) then I'd favour nuking the directive. > Ok, so I just noticed you were talking about > ap_register_output_filter_protocol() and not ap_register_output_filter() so > I guess the change above is pretty useless. Look at the header file. ap_register_output_filter is from 2.0. In 2.2 it's just a #define, with the last argument (proto flags) zero. -- Nick Kew --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|