0

While testing I observed that media attachments more than 4194304 bytes are rejected by the proxy. It throws the message - "HTTP content length exceeded 4194304 bytes".

Is this the functionality of LittleProxy implementation or there is any configuration which will allow bigger size of attachments than this?

AnilJ
  • 1,951
  • 2
  • 33
  • 60

1 Answers1

2

This sounds like a TooLongFrameException thrown by HttpObjectAggregator.

The only way that I think this could happen is when using an HttpFiltersSource that specifies a non-zero value from getMaximumRequestBufferSizeInBytes() or getMaximumResponseBufferSizeInBytes(). You can increase those, but that increases your memory usage. If the filter can be rewritten so as to work with frames (chunks) as they stream through, then you can set the buffer size to 0 and dramatically reduce your memory consumption.

user3074401
  • 36
  • 1
  • 1
  • I found the code in my application which was setting this limit. However I did not quite get one thing, how the filter can work at the frame (or chunk) level by itself. If I understood it correct, it is upto the content server, which serves the content, decides how to serve it. The filter is running at the Proxy sitting in between. In case of progressive download video, the content typically comes as a blob. AFA video streaming is concerned, at TCP level GoP boundaries are not guaranteed. In case of adaptive streaming, the content server (eg Youtube) itself serves the content in chunked form. – AnilJ Dec 08 '13 at 07:03