you may stop it by deleting the generated *.java files
for your jsp-page(s) in the "work" directory of tomcat.
-Ursprüngliche Nachricht-
Von: Frank Lawlor [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 9. Mai 2001 17:34
An: Tomcat (E-mail)
Betreff: Odd Page Caching Behavior
Sometimes a
yep, i posted about this problem some days ago, with no reply.
obviously a bug in the connector, which (by mistake) expects
a Unicode-Charset.
*stefan
-Ursprüngliche Nachricht-
Von: Andreas Schlegel [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 26. April 2001 11:57
An: [EMAIL PROTECTE
Are you using jdk 1.3 on unix ? I had the same problem with
special characters and solved it by setting the system
variable "LC_CTYPE" correctly. (must be set and exported
before the jvm with tomcat is started) In my case, the
correct value was "de_DE", in your case it probably would
be "fr_FR" ..
Maybe I can help you with the second question at least:
I removed the default host and put several virtual hosts in
my server.xml and some of them contain the same path "/". It
works just beautifully. Maybe you throw out the default host
like I did. If tomcat works like apache, it will use the
f
hi,
i have run into a problem with non ascii-url characters.
When there is e.g. the German ä = ä in an URL,
I have to encode it as follows:
APACHE alone, non-ascii character anywhere:
http://mydomain.de/d%E4mlich.html
TOMCAT standalone, non-ascii character anywhere:
http://mydomain.de:8080/req
Donnie,
thank you for your hint. I have experienced similar problems with solaris 8 and
tomcat 3.2.1. However I regret that I do not understand the mentioned problem:
> 6.11 Misconfiguration Can Cause CPU-Bound Loop
>
> If you misconfigure Tomcat 3.2 in a way that there is no valid context to
>
Hi,
I've seen this question beeing asked a few times in the
archives, but I didn't find any replies:
How do I restrict access to tomcat listening e.g.
on port 8007 for incoming requests from e.g. apache,
using e.g. mod_jk ?
There seems to be no possibility in the configu
IE has some strange caching policies. By saying "when the user JUST
comes back ..." do you mean "when he hits the [back]-Button or uses
javascript:history.back()" ? In this case, IE5.5 applies some kind
of timeout-rule: if you hit "back" within a short intervall, it will
display the cache, no matt
Maybe you are using mod_jk with ajp13 ? It was not able to handle
file uploads until tomcat 3.2.2b2. I ran into this problem and
simply switched to ajp12.
*stefan
- original message -
Von: Arendsen, Alef [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 13. März 2001 11:15
An: '[EMAIL PROTE
