-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mark,
On 06/20/2014 02:07 PM, Mark Thomas wrote:
On 20/06/2014 11:58, Björn Höfling wrote:
Hello,
summary of my Problem:
When a client POSTs with Tranfer-Encoding:chunked, my server is
not processing the request.
Full details:
I
Just to update, instead of using Valve I re-build the tomcat with following
code while setting Expiry header cookie.setSecure(request.isSecure()) in
SingleSignOn class file.
This works. In this way I can probably make it as secure or empty the value.
-Original Message-
From: Radha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 6/21/14, 9:46 AM, André Warnier wrote:
Christopher Schultz wrote:
The OP. Look up in the configuration: the executable is set to
perl.
That's just the default, as it comes in the standard Tomcat
distribution. See also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Björn,
On 6/23/14, 7:52 AM, Björn Höfling wrote:
Hi Mark,
On 06/20/2014 02:07 PM, Mark Thomas wrote:
On 20/06/2014 11:58, Björn Höfling wrote:
Hello,
summary of my Problem:
When a client POSTs with Tranfer-Encoding:chunked, my server
2014-06-23 18:27 GMT+04:00 Christopher Schultz ch...@christopherschultz.net:
Thanks for the hint. Should have thought of it before asking the
list! Updating takes some time, I will provide feedback when all is
done.
$ tar xzf /path/to/tomcat-...tar.gz
$ $CATALINA_HOME/bin/catalina.sh stop
Moving the SSL port from 8443 to 443 has solved the problem. It appears that
when the url www.something.net is entered, Firefox remembers that this is an
SSL site and automatically add the s to get https. In fact after the timeout
the url line in the browser shows https:www.something.net.
Hi,
I have I server with Apache and Tomcat through jk_mod and the perfonrmance
is awful. This is mostly confined to images as far as I know, but it is
hard to tell.
The images are served from Apache with the help of the following lines:
# Serve static content from /resources and /data using
