On Wed, 2011-06-15 at 13:11 -0500, Jason Funk wrote:
>
> User Makes Request- > Web Server processes and generates output -> My
> module analyzes ouput determines whether it should be passed back to the
> user or not.
Sounds like you have the right one, an output filter. However, should
it re
"Does it transform the content from one representation
to another, or is it actually something else, like an access,
authorization or authentication module?"
It fits much more cleanly in the "access, authorization, or authentication
module" category. But the decision to complete the request is det
> > > I am writing an output filter module that will under some
> > > circumstances want to send back an HTTP Error Code and kill
> > > the request without sending back the content.
...
> > The only way you can affect a response status is to return an
> > error to your caller before passing anythin
So what option do I have? Cache all the buckets of the request without
passing anything down the chain so I can make the decision about what to do?
Would that even require caching them in the filter's ctx?
Do I have any other choice?
On Tue, Jun 14, 2011 at 5:12 PM, Nick Kew wrote:
> On Tue, 14
On Tue, 14 Jun 2011 16:31:22 -0500
Jason Funk wrote:
> I am writing an output filter module that will under some circumstances want
> to send back an HTTP Error Code and kill the request without sending back
> the content.
You can't set an HTTP response code when one has already been sent
down t
