From: Matthew G. <mat...@gm...> - 2011-07-11 21:37:48
|
Resteasy - or more likely the container which is running your app - may choose to use "Transfer-Encoding: chunked" for large responses. This allows it to start sending data before the whole response size is known. In that case the Content-Length header is omitted. Your downstream clients should handle OK as it's part of the HTTP 1.1 spec. http://en.wikipedia.org/wiki/Chunked_transfer_encoding Cheers! mg On Mon, Jul 11, 2011 at 8:26 PM, Neil Chaudhuri <nch...@po...> wrote: > I have noticed that RESTEasy responses vary in whether the Content-Length > header is set or not. I haven't done any fine-grained analysis, but > empirically it seems that responses < 10K have the Content-Length header set > while those larger do not. Again, that 10K figure is only a guess, but there > is definitely some threshold where the Content-Length header ceases to be > set. > Is there any reason why this would be the case? It turns out that the > presence/absence of this header has some significance for us downstream. > Thanks. > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Resteasy-developers mailing list > Res...@li... > https://lists.sourceforge.net/lists/listinfo/resteasy-developers > > |