Hi Friends,
I am seeing a problem with my servlet running in
Tomcat and I'm a bit baffled.
When I post a base64 encoded string that has a +
character in it from a client to my servlet (via
form post), the string becomes disjointed at +
character making it two strings. That is, the +
Hi Folks!
What is the best way for an administrator to tell
Tomcat (or maybe tell a specific servlet) to
temporarily stop accepting new requests for a running
servlet?
I'm thinking of a scheme like this: I put code in the
servlet doGet()/doPost() processing block of the
servlet and have it
Hi All,
I just wanted to know if I can first obfuscate my
selvlet
with ProGuard before I deploy it in Tomcat
environment.
Will doing this really protect my servlet and make it
really difficult for someone to reverse engineer or
decompile it, as people seem to say?
Thank you.
Jeng
--- Mark Thomas [EMAIL PROTECTED] wrote:
Jeng Yu wrote:
Interestngly, the same RSA public encryption code
with
Bouncy Castle library works flawlessly when I
develop
it in Netbeans IDE and run it as a java
application
(not servlet). In servlet environment, it fails.
Yes,
I added
class fortune.Fortune.
What am I not doing right? Has anyone else seen
something similar and what's the
getaround/workaround?
Thanks,
Jeng Yu
-
To start a new topic, e-mail: users@tomcat.apache.org
Hello Good People!
I need your help! I can't find a good answer where
I've
looked. Here's my problem:
I have a web application client that shows a user a
form to fill out and then submits the form input to a
servlet in an application server (Appserver A) running
Tomcat.
The servlet (in
--- Peter Crowther [EMAIL PROTECTED]
wrote:
From: Jeng Yu [mailto:[EMAIL PROTECTED]
The servlet (in Appserver A) then processes part
of
the
form input in the doGet method and then needs to
send
the rest of the form to another web server
(Appserver B) to process and return
