Re: Filter question in 4.1.18, can my filter get unchunked and unzipped requests?

[Bill Barker <wb...@wilshire.com>]

"Donie Kelly" <do...@tecnomen.ie> wrote in message 
news:13B821B74AFB8442AC990AC39618581FAE8D05@atlantis.tecnomen.ie...
> Hi all
>
>
>
> I've been reading up on filters to see if I can find a solution to an
> annoying problem. I can't find it so I'm looking here.
>
>
>
> I have this http filter that messes with the http request and response
> before it enters and leaves tomcat. The problem is that this filter works 
> at
> a fairly low level on the data but a big mistake we made is that it 
> assumes
> that the data is neither chunked or gzipped. Now we have a situation where
> some clients send data either in chunked form or gzipped form and out 
> fairly
> complicated filter gets very confused as it's not expecting this.
>
>
>
> Ok, we can re-write the thing to handle this but doesn't tomcat already
> unzip and de-chunk data? Problem is where is it done?
>
>
>
>
>
> My question is, how can we arrange it so that the initial processing on 
> the
> incoming data is done by tomcat so that it unzip and de-chunks the data
> before it reaches my filter?
>
>
>
> Is this possible???
>
>
>
> Please say it is....
>
>

You may need to plug in a newer Coyote Connector (or, even, plug it in in 
the first place, since 4.1.18 is a bit old :), but it will at least unchunk 
the input for you.  It doesn't currently unzip for you, but that should be a 
lot less common.



>
> Many thanks
>
> Donie
>
>
>
> 




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org