You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the following problem: For certain hosts, I'd like to access POST request data and respond with a response directly ("short-circuit response").
I know it can be achieved by returning a positive buffer size in getMaximumRequestBufferSizeInBytes(), but from my understanding this will prevent the user from uploading data larger than said size. The POST requests I'm interested in are a few kilobytes in size, and are only destined for a certain host. All the other POST requests I'm not interested in and I'd just like to stream-through, without buffering.
From my understanding of the interaction between LittleProxy and Netty this can not be achieved, as the content aggregation (instantiation of HttpObjectAggregator and adding it to pipeline) is configured on the channel basis and not per-request. At channel initialization time we don't know the target host because it is contained in the request. Also, the channel represents the client-to-proxy TCP connection, which i believe can persist over several requests (keep-alive) and possibly over multiple target hosts (I'm unsure about the last one, but can't rule it out)?
Is there some other way to achieve this?
The text was updated successfully, but these errors were encountered:
I have the following problem: For certain hosts, I'd like to access POST request data and respond with a response directly ("short-circuit response").
I know it can be achieved by returning a positive buffer size in getMaximumRequestBufferSizeInBytes(), but from my understanding this will prevent the user from uploading data larger than said size. The POST requests I'm interested in are a few kilobytes in size, and are only destined for a certain host. All the other POST requests I'm not interested in and I'd just like to stream-through, without buffering.
From my understanding of the interaction between LittleProxy and Netty this can not be achieved, as the content aggregation (instantiation of HttpObjectAggregator and adding it to pipeline) is configured on the channel basis and not per-request. At channel initialization time we don't know the target host because it is contained in the request. Also, the channel represents the client-to-proxy TCP connection, which i believe can persist over several requests (keep-alive) and possibly over multiple target hosts (I'm unsure about the last one, but can't rule it out)?
Is there some other way to achieve this?
The text was updated successfully, but these errors were encountered: