I'd add response time logging %D to the access log config to see if requests
are slow
You can add that to jetty too.
Stefan
Sendt fra min iPhone
Den 26. nov. 2014 kl. 14.34 skrev Kristian Rink kawazu...@gmail.com:
Hi Nick;
thanks for your comment.
Am 26.11.2014 um 14:11 schrieb
Check user-agent header too. Mobile phones might just be too slow or get
disconnected
Sendt fra min iPhone
Den 26. nov. 2014 kl. 15.11 skrev Kristian Rink kawazu...@gmail.com:
Am 26.11.2014 um 14:48 schrieb Stefan Magnus Landrø:
I'd add response time logging %D to the access log config
still check
if the data is chunked, is that incorrect?
On 13 Nov 2014, at 18:52, Stefan Magnus Landrø stefan.lan...@gmail.com
wrote:
The transfer encoding header is missing, right?
Sendt fra min iPhone
Den 13. nov. 2014 kl. 18.13 skrev Blomme Dieter
dieter.blo...@digipolis.be
I highly recommend Gatling for load testing. It features non blocking io and
can easily drive 50.000 connections from one machine.
Nice DSL too.
Stefan
Sendt fra min iPhone
Den 17. nov. 2014 kl. 22.29 skrev Rose, John B jbr...@utk.edu:
| Maybe the question is what combination of load
Hi there,
We're seeing some weird behaviour in our access logs.
For around 13 minutes we see entries from requests received several minutes
before it actually gets logged (the two timestamps on the same line are up
to 13 minutes apart! ).
The number to the far right is %D - the response time
The transfer encoding header is missing, right?
Sendt fra min iPhone
Den 13. nov. 2014 kl. 18.13 skrev Blomme Dieter dieter.blo...@digipolis.be:
Hi,
We have a problem with mod_proxy and chunked content.
We use mod_proxy to selectively request pages from a second site, the
ProxyPass and
