Which version of Tomcat are you using?
p
On 12 April 2010 01:35, Sam Stephens samspad...@gmail.com wrote:
Hi all.
The tomcat documentation says the following:
If the web application is packaged as a WAR then /META-INF/context.xml
will be copied to
If you're uploading directly to the webapps directory, try uploading the
file renamed to yourapp.warTMP and renaming it in place when the upload is
complete.
Please let us know if this works/does not work.
p
On 12 April 2010 09:18, Pid * p...@pidster.com wrote:
Which version of Tomcat are
I've tried that, it doesn't work. Updating a WAR file will trigger an
undeploy and consequent removal of the context descriptor in a running
Tomcat if the Host autoDeploy attribute is true.
If autoDeploy is false, redeploy without updating the context.xml can occur
using the manager.
p
On 12
No, the logon page is very simple, without the navigation bar, so it doesn't
link that page
-Original Message-
From: Pid * [mailto:p...@pidster.com]
Sent: Friday, April 09, 2010 5:53 PM
To: Tomcat Users List
Subject: Re: Tomcat 6.0.24 requires me to log on twice
Terry, does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry,
On 4/9/2010 12:14 PM, Terry Horner wrote:
The problem seems to occur if there are any restricted resources
within a page - it doesn't seems too outlandish for someone to
restrict access to their images folder (say, it has client
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Friday, April 09, 2010 5:55 PM
To: Tomcat Users List
Subject: Re: Tomcat 6.0.24 requires me to log on twice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry,
On 4/9/2010 12:08 PM, Terry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/U,
On 4/10/2010 3:31 PM, /U wrote:
Connector port=443 protocol=HTTP/1.1 SSLEnabled=true
maxThreads=150 scheme=https secure=true
clientAuth=false sslProtocol=TLS
keystoreFile=/users/me/.keystore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
/U,
On 4/10/2010 4:13 PM, /U wrote:
i am confused about one thing: whil keystore is explicitly specified
in connector config, what about the truststore?
It can also be configured in the Connector. Have you not read any of
the documentation?
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry,
On 4/12/2010 8:05 AM, Terry Horner wrote:
That would be illogical, but it's not what I'm doing - in our system (and in
the hypothetical example) the restricted images are inside a restricted page.
The bookmarks are to a restricted page,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry,
On 4/12/2010 9:23 AM, Terry Horner wrote:
Looking at old logfiles from slightly older tomcat 6.0 versions this seems to
be normal - this request in the last step in the request data page-get sent
to logon page-send username and
That works in that my filter is called when the session times out and the user
is redirected to the login page. However, the Referer header makes no
indication that the user is logging in. In Jetty, the Referer header would be
/login.do. This would indicate that the user is logging in. If
That was my first thought, as I was copying from previously downloaded
files, and I'd see the same symptoms in a known instance of mismatch.
So I went to the Tomcat Archives and downloaded them again, making sure
I was in the 32-bit tree. The posted catalina.log is the result of that
latter
*** NOTICE *
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is privileged,
confidential, and exempt from disclosure under applicable law. If the
reader of
2010/4/12 Jeffrey Janner jeffrey.jan...@polydyne.com
Subject: RE: Which native library?
Hi Chris -
The only thing I was doing was replacing the existing file in the Tomcat\bin
directory and restarting.
I had 1.1.3 (which was downloaded by the installer) working. So I stopped
Tomcat,
The request object in the servlet spec as I understand it as used in the
Tomcat 6 container for example makes use of the deprecated HTML
attribute name in order to tie individual elements of a HTML form to
server-side variables. This seem to imply that in order to produce
working Servlets one has
On Mon, Apr 12, 2010 at 8:00 AM, MB digital.disc...@gmail.com wrote:
The request object in the servlet spec as I understand it as used in the
Tomcat 6 container for example makes use of the deprecated HTML
attribute name in order to tie individual elements of a HTML form to
server-side
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, April 12, 2010 2:48 PM
To: Tomcat Users List
Subject: Re: Tomcat 6.0.24 requires me to log on twice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry,
On 4/12/2010 9:23 AM, Terry
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, April 12, 2010 2:40 PM
To: Tomcat Users List
Subject: Re: Tomcat 6.0.24 requires me to log on twice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry,
On 4/12/2010 8:05 AM, Terry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul,
On 4/11/2010 7:11 PM, Paul Carroll wrote:
I am using Tomcat 6.0 on Windows Server 2003. It seems that when my
session expires I am redirected to the login page which I would
expect. However, my filter is not called when I am redirected to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul,
On 4/11/2010 7:11 PM, Paul Carroll wrote:
I am using Tomcat 6.0 on Windows Server 2003. It seems that when my
session expires I am redirected to the login page which I would
expect. However, my filter is not called when I am redirected to
I'm running Tomcat 5.5.17 as a service on Windows 2000 SP4 w/native-APR
1.1.18.
I've got the following connector configured:
Connector address=172.16.9.1 port=443 maxHttpHeaderSize=8192
maxThreads=150 minSpareThreads=5 maxSpareThreads=75
enableLookups=false
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 4/12/2010 12:57 PM, Jeffrey Janner wrote:
I'm running Tomcat 5.5.17 as a service on Windows 2000 SP4 w/native-APR
1.1.18.
FYI tcnative is at 1.1.20, now, and TC 5.5 is at 5.5.28. Always good to
be up-to-date if you can afford to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 4/12/2010 1:51 PM, Christopher Schultz wrote:
Jeffrey,
On 4/12/2010 12:57 PM, Jeffrey Janner wrote:
I'm running Tomcat 5.5.17 as a service on Windows 2000 SP4 w/native-APR
1.1.18.
FYI tcnative is at 1.1.20, now, and TC 5.5 is at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry,
On 4/12/2010 11:38 AM, Terry Horner wrote:
The webapp is one of two in a single sign-on environment, and listens
on /. The other webapp is a simple one used to provide a client with
a customised login page (they go to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terry,
On 4/12/2010 11:23 AM, Terry Horner wrote:
org.apache.catalina.valves.ExtendedAccessLogValve the definition is within
the host, not the context.
The log pattern string is now
c-dns x-H(remoteUser) date time x-H(protocol) cs-method
Hi,
Recently we migrated from Weblogic to Tomcat 5.5.28. After the migration
we had issues in viewing special characters in UI, we updated UTF-8
encoding settings to web.xml and in TOMCATINSTALLDIR/conf/server.xml
added the URIEncoding parameter to the connector.
Web.xml settings
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
MB,
On 4/12/2010 11:00 AM, MB wrote:
The request object in the servlet spec as I understand it as used in the
Tomcat 6 container for example makes use of the deprecated HTML
attribute name...
+1 to Hassan's comments: the HTML attribute name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill,
On 4/10/2010 5:33 PM, Bill Barker wrote:
Another thing to note is that the Tomcat folks have made an unstable
change, here, by changing a public API. It would have been better to
create a method with a new signature and deprecated the old
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jagan,
On 4/12/2010 2:45 PM, Ramachandiran, Jagan Mohan [OCDUS Non JJ] wrote:
Recently we migrated from Weblogic to Tomcat 5.5.28. After the migration
we had issues in viewing special characters in UI, we updated UTF-8
encoding settings to web.xml
I stand corrected. It seems that the elements: a, button, form, img,
input, map, meta, object, select, param and textarea can have the
attribute name under HTML 4.01 Strict. In the case of map and param
it is even mandatory.
Sorry for top-posting. I must change my gmail settings
2010/4/12
i am combininig multiple security-constraint and wildcard pattern. The
result is a bit confusing.
only and single security-constraint def:
===
security-constraint
web-resource-collection
web-resource-nameHTMLManger and Manager command/web-resource-name
url-pattern/*/url-pattern
in my case, i am testing with clients authenticating to tomcat with dod cac
cards. (smartcards)
i downloaded the dod root p7b cert files
i checked/verified the root cert for the client cac card certs,
matched the dod root certs (in the p7b files)
i extracted ONLY the root cert's from each
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel,
On 4/12/2010 4:38 PM, aldana wrote:
This is counterintuitive, I would still expect 'admin' to access all
ressources, because it has /* wildcard.
After debugging tomcat confirms, adding constraints is side-effecting
exististing
Thanks for the earlier replies.
So after some more research it seems there is no way to tell tomcat
that I don't want particular directories to be deleted on an
application redeploy? Is this correct ?
I have a forum application. When we update it we want to distribute a
new war file (previously
On Mon, Apr 12, 2010 at 6:08 PM, Sam Stephens samspad...@gmail.com wrote:
I have a forum application. When we update it we want to distribute a
new war file (previously we updated all files individually). If we
give out a new war file to our customers the images directory, the
attachments
I set following statement in conf/server.xml, it can run well before
tomcat6.0.20,when I modify class file,tomcat can reload automaticly.
Context path=/Test docBase=Test reloadable=true
crossContext=true/Context
But when I use tomcat 6.0.2,I find it can't reload automaticly,why? Where is
wrong?
36 matches
Mail list logo
