No common browsers support HTTP/1.1 trailers. Look at the column “Headers in trailer” in the “Network” tab of browserscope. Chrome: No, and won’t fix (bug). Supports H/2 trailers (bug). Firefox: No, and I don’t see a ticket in bugzilla for it. Appears to support H/2. IE: No Edge: No Safari: No Opera: Old versions only … Read more
Below is a copy of an example trailer I copied from The TCP/IP Guide site. As we can see, if we want to use trailer header, we need add a “Trailer:header_name” header field with a header name and then add the trailer header entity after chunked body area. We can add 0 or more trailer … Read more
I don’t know which server connector you use for your application but it seems that it’s the default one. Restlet is pluggable and extensible at different levels. I recommend you to use the Jetty one. To do that simply add the JAR file for the Jetty extension (org.restlet.ext.jetty.jar) within your classpath. The connector will be … Read more
In case the other answers weren’t clear enough: First you gzip the body with zlib (this can be done in a stream so you don’t need the whole thing in memory at once, which is the whole point of chunking). Then you send that compressed body in chunks (presumably the ones provided by the gzip … Read more
Use Content-Length, definitely. The server utilization from this will be almost nonexistent and the benefit to your users will be large. For dynamic content, it’s also quite simple to add compressed response support (gzip). That requires output buffering, which in turn gives you the content length. (not practical with file downloads or already compressed content … Read more
OK. I’ve triple-tested this and I am 100% sure that it is being caused by my anti-virus (ESET NOD32 ANTIVIRUS 5). Whenever I disable the Real-Time protection, the issue disappears. Today, I left the Real-Time protection off for 6-7 hours and the issue never occurred. A few moments ago, I switched it back on, only … Read more