Adrian Beech wrote:
Hi all,
A work colleague mentioned on Friday it would be better to place objects
(beans and the like) which had been created in a servlet into the request
context when exposing them to the JSP. To date all the code I've written
stores beans and the like in the session
Glad to see I'm not alone ;-)
FYI, the tomcat plugin for Eclipse from Sysdeo
(http://www.sysdeo.com/eclipse/tomcatPlugin.html)
contains a classloader that takes classes from various locations.
I've been using it for a while now and it works perfectly.
The equivalent for non-java classes (jsp,
Hello!
Can somebody help me, please?
My OS is Suse 9.2 pro. Apache and Tomcat work for me.
But If I start Apache with normal httpd.conf, Apache works for me.
If I paste my lines for Apache-Tomcat Connection, Apache doesn't
work for me, only Tomcat. It must be something wrong with this lines, but
Hi,
I have a apache https enabled webserver and tomcat server an and am
using the mod_jk connection module. From all the documentation I have
read, it indicates that apache handles all the SSL negotiations and that
the traffic between apache and tomcat is clear text. How can I enable
Liz Donaldson wrote:
Hi,
I have a apache https enabled webserver and tomcat server an and am
using the mod_jk connection module. From all the documentation I have
read, it indicates that apache handles all the SSL negotiations and that
the traffic between apache and tomcat is clear text.
Thanks for quick reply!! Yes my tomcat server is behind the firewall,
but corporate security guidelines also is demanding that the
communications between apache and tomcat be ssl encrypted. I am going to
check out stunnel.org.
Thanks!
Michael Echerer wrote:
Liz Donaldson wrote:
Hi,
I
5.5.9's documentation for the standard HTTP connector
says, in SSL Support
sslProtocol
The version of the SSL protocol to use.
If not specified, the default is TLS.
If I configure my HTTPS connector with the (supposedly
redundant) attribute
sslProtocol=TLS
then it works fine, but
I believe that a keystore can legitimately contain
many certificates, whether root- or self-signed.
How does (and should) Tomcat 5.5.9 choose which of
many such certificates to offer when a client makes
an HTTPS request?
Is there any way of hinting or telling it which to
use (to help me
I run 5.5.9 standalone under Fedora Core 3, and
have ten consecutive IP addresses on one NIC.
When I configure a standard HTTP connector without
any particular IP address, it seems to happily accept
requests on all these addresses (is this by design?)
When I configure it with the extra
Paul Singleton [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I believe that a keystore can legitimately contain
many certificates, whether root- or self-signed.
How does (and should) Tomcat 5.5.9 choose which of
many such certificates to offer when a client makes
an HTTPS
Hi all.
I have been mucking around this for some time and have some empirical
data and a question for the list.
BACKGROUND
---
I'm building a web client for a RMI client/server application. RMI
server and client are working from command line. Next I built
JSP/Servlet which
With 5.5.9 (or the latest 5.0.x?) should I be able
to configure more than one virtual HTTPS host, each
with its own root certificate? e.g.
Server port=8005 shutdown=SHUTDOWN
Service name=ABC
Connector address=195.108.201.212 port=8443
scheme=https secure=true/
From: Paul Singleton [mailto:[EMAIL PROTECTED]
Subject: sslProtocol default value in 5.5.9 - broken?
Am I missing something, is this a documentation bug
or a Tomcat bug?
Can't really answer your question, but I did verify the same apparently
erroneous behavior on one of our TC 5.5.9
Hi Angela,
Not sure why it works fine with Tomcat 5 but followings is my view to the
problem with the login page.
1. The security constraint for the images and CSS tells that the GET and
HEAD methods to these resources ARE protected.
2. When you go to the login page, as it tries to get the
From: Paul Singleton [mailto:[EMAIL PROTECTED]
Subject: binding 5.5.9 HTTP connector to specific IP address
When I configure it with the extra attribute
address=195.108.201.212
(not the real address) then Tomcat seems
to start up happily
snip
but requests to that IP address fail with
Hello,
We have a server running Tomcat 4.1.27, mod_jk2, Apache2
hosting 6 applications. Tomcat Manager shows number of
active sessions for each application. At one time one of
the applications had over 300 active sessions, but
applications user monitor would show only 60 authenticated
users. I
There is 2G Ram in my pc.
I had installed a antiVirus software in my pc, but I had exclude the folder
which the web application and database files located, It won't be another
applicate access the file .
B.R.
Ivy
- Original Message -
From: Sir John Nueva [EMAIL PROTECTED]
To: Tomcat
Here is my guess.
Case 1: Your security setting is interfering with tomcat. Try turn off your
firewall
and see if you still have the problem[make sure you are not connected from
internet while doing this]
Is your w2k a Server or client? What port are you using[80/8080]?
Case 2: Your JDK is not
Apache web server's SSL certificate was already configured by our client so
i did't ve to configure anything on apache. But we did configure SSL on
tomcat.
When redirecting, redirect through apache web server's port instead of
tomcat's port, because now your requests are being processed by apache
Issue Resolved:
It was not the issue of mod_jk or tomcat either. It's the issue of Unix
shell from where I was starting tomcat. The thing which works for me is to
run tomcat in CSH Shell and in background.
Dear Pierre Aliye! Thanks a lot for your great support.
Regards,
Muhammad Owais Ansari
20 matches
Mail list logo
