Yea, that is the approach I've been thinking. I just wanted to remain servlet container agnostic as much as possible. Thanks for the suggestion.
On Sun, Jan 12, 2014 at 2:39 AM, Simone Bordet <[email protected]> wrote: > Hi, > > On Sat, Jan 11, 2014 at 3:33 AM, Gaurav Kumar <[email protected]> > wrote: > > I don't want http client to handle any chunk encoding because I want to > > write the bytes back to a servlet outoutstream so that browser can do > chunk > > encoding processing. > > And why you want to do that ? > > It looks like you're using HttpClient as a proxy. > Jetty comes with a built-in module to do that, see jetty-proxy and > ProxyServlet ( > http://www.eclipse.org/jetty/documentation/current/proxy-servlet.html). > > How HttpClient receives the content and how you write it to a > ServletOutputStream are two different things. > You can receive non-chunked content and chunk it by simply calling > response.flushBuffer() in the ServletOutputStream. > > -- > Simone Bordet > ---- > http://cometd.org > http://webtide.com > http://intalio.com > Developer advice, training, services and support > from the Jetty & CometD experts. > Intalio, the modern way to build business applications. > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
