Andreas Deller wrote:
Thanks for the optimization hint, although we don't encounter performance
problems so far.
APR just leverages OS native functionality, it's a gain rather than a
correction.
In the former case, I'd try to eliminate the room for error between
versions by standardising JV
Pid wrote:
Andreas Deller wrote:
Pid wrote:
Andreas Deller wrote:
Hi
I have activated LiveHttpHeaders and the RequestDumperValve and
fortunately ran into the problem in my development environment.
Sorry for the long posting, but it seems necessary to me.
Important notes:
- Between the client
Andreas Deller wrote:
Pid wrote:
Andreas Deller wrote:
Hi
I have activated LiveHttpHeaders and the RequestDumperValve and
fortunately ran into the problem in my development environment.
Sorry for the long posting, but it seems necessary to me.
Important notes:
- Between the client and the ser
Pid wrote:
Andreas Deller wrote:
Hi
I have activated LiveHttpHeaders and the RequestDumperValve and
fortunately ran into the problem in my development environment.
Sorry for the long posting, but it seems necessary to me.
Important notes:
- Between the client and the server, there is a reverse
Andreas Deller wrote:
Hi
I have activated LiveHttpHeaders and the RequestDumperValve and
fortunately ran into the problem in my development environment.
Sorry for the long posting, but it seems necessary to me.
Important notes:
- Between the client and the server, there is a reverse proxy.
RD
Hi
I have activated LiveHttpHeaders and the RequestDumperValve and
fortunately ran into the problem in my development environment.
Sorry for the long posting, but it seems necessary to me.
Important notes:
- Between the client and the server, there is a reverse proxy.
- After all, this is *one*
Could it be that you have a problem with caching? What are the exact
headers (via LifeHTTPHeaders) sent by/to the client
a) when it works
b) when it doesn't work?
Greg
--
what's puzzlin' you, is the nature of my game
gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2
gpgp-key available @ http://p
Hi
A typical entry looks like this:
192.168.11.11 - - [05/Jan/2007:11:23:59 +0100] "GET
/ebanking/css/custom.css HTTP/1.1" 200 -
"https://some.bank.ch/ebanking/login"; "Mozilla/4.0
(compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)"
The files are all correct, since they most of the time a
Andreas Deller wrote:
Andreas Deller wrote:
Hi
A typical entry looks like this:
192.168.11.11 - - [05/Jan/2007:11:23:59 +0100] "GET
/ebanking/css/custom.css HTTP/1.1" 200 -
"https://some.bank.ch/ebanking/login"; "Mozilla/4.0
(compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)"
The files
Andreas Deller wrote:
Hi
A typical entry looks like this:
192.168.11.11 - - [05/Jan/2007:11:23:59 +0100] "GET
/ebanking/css/custom.css HTTP/1.1" 200 -
"https://some.bank.ch/ebanking/login"; "Mozilla/4.0
(compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)"
This results in the client gettin
Andreas Deller wrote:
Hi
A typical entry looks like this:
192.168.11.11 - - [05/Jan/2007:11:23:59 +0100] "GET
/ebanking/css/custom.css HTTP/1.1" 200 -
"https://some.bank.ch/ebanking/login"; "Mozilla/4.0
(compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)"
This results in the client gettin
Hi
A typical entry looks like this:
192.168.11.11 - - [05/Jan/2007:11:23:59 +0100] "GET
/ebanking/css/custom.css HTTP/1.1" 200 -
"https://some.bank.ch/ebanking/login"; "Mozilla/4.0
(compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)"
This results in the client getting back a 200, but no co
Andreas Deller wrote:
Hi
I posted this unsuccessfully a week ago under
'Tomcat 4.1.30/5.0.28 empty responses - return code "200 -"',
so I rephrase and shorten my question.
OS: Solaris & Debian, Tomcat version 4.1.30 and 5.0.28.
In the access logs, there are a number of entries with the HTTP
st
Hi
I posted this unsuccessfully a week ago under
'Tomcat 4.1.30/5.0.28 empty responses - return code "200 -"',
so I rephrase and shorten my question.
OS: Solaris & Debian, Tomcat version 4.1.30 and 5.0.28.
In the access logs, there are a number of entries with the HTTP
status code "200 -". So t
14 matches
Mail list logo