Daniel,
On 6/26/23 12:47, Daniel Andres Pelaez Lopez wrote:
Hi Tomcat community,
I have a requirement where we want to manually decode a Chunked Transfer
Encoding (CTE) stream using CoyoteInputStream to have access to the chunk
size. This means I want to use CoyoteInputStream.read method and get the
whole CTE bytes. Saying it in another way: we want to decode the CTE at
hand skipping Tomcat defaults.
Dumb question: why?
The current flow from the point of view of CoyoteInputStream is:
CoyoteInputStream.read -> Request.read -> ChunkedInputFilter.read.
ChunkedInputFilter handles the CTE decoding and the read method only
returns the chunks, with no other information, like chunk size.
I found that the method Request.setInputBuffer might allow to set a
different InputBuffer implementation, for instance, the
IdentityInputFilter, which I understand returns all the stream bytes, with
no decoding. However, not sure if this is the right way and which
consequences might have.
I would like to know if there are other ways to override the CTE behavior,
any help would be appreciated.
A problem I can see is that you are working with a blocking streaming
interface e.g. read(byte[]) and you also want to get the chunk size.
When? The chunk-size can change for every chunk, so if you call
getChunkSize() before the read() and after the read(), they may be
different if the read() returns data from multiple chunks. It may have
changed multiple times between read() was called and when it completed.
If you want to always size byte byte[] to read full-chunks at once ... I
guess I would again ask "why?"
Would it be sufficient for ChunkedInputFilter to maybe send an
event-notification each time a chunk boundary was crossed? For example:
public interface ChunkListener {
public void chunkStarted(ChunkedInputFilter source, long offset, long
length);
public void chunkFinished(ChunkedInputFilter source, long offset,
long length);
}
Then, every time the Filter begins or ends a chunk it could notify your
code and you can do whatever you want with that information.
You might be able to subclass the (somewhat confusingly-named)
ChunkInputFilter and bolt-on your own logic like what I have above.
BTW: We are using Spring Boot with Tomcat embedded.
That probably makes it much easier to tamper with the setup, thanks for
providing that information.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
