Thanks, good hint. I was thinking that myself overnight.
Here's the basic scenario:
I use the main request handler to generate XML. I have a framework that
allows me to glue together various sub-handlers (from my framework, not
Apache handlers) to add disparate data elements into the XML
Sounds like something I would *not* do. If you are going to return a
404, why not do it as soon as possible.
Generating data only to return a 404 sounds like useless extra work
unless you are caching the same data for future requests.
On 12/17/07, Marc M. Adkins [EMAIL PROTECTED] wrote:
Thanks,
[EMAIL PROTECTED] wrote:
Sounds like something I would *not* do. If you are going to return a
404, why not do it as soon as possible.
Generating data only to return a 404 sounds like useless extra work
unless you are caching the same data for future requests.
I agree, if you don't want to
I'm actually thinking the same thing. I've been looking for a
configuration setting that will just notice that the file isn't there
and 404, but I think the fact that there IS a response handler is
causing Apache to skip the check for the existence of the file. Failing
a simpler
Implemented Fixup handler and it works fine. Thanks all.
Marc M. Adkins wrote:
I'm actually thinking the same thing. I've been looking for a
configuration setting that will just notice that the file isn't there
and 404, but I think the fact that there IS a response handler is
causing Apache
