RE: Forwarding with parameters
You cannot change protocol inside a reuqest. To change protocol you have to send a redirect to the browser. -Original Message- From: Gil Hauer To: Tomcat Users List Sent: 24-07-03 13:44 Subject: Forwarding with parameters Hello, I have code in a servlet that, based on transaction status, forwards to another target page. The code snippet is: String target = /index.jsp; ServletContext c = getServletContext(); RequestDispatcher d = c.getRequestDispatcher(target); response.setContentType(text/html); d.forward(request, response); How can I set new parameters for the target page? Is it as simple as setting String target = /index.jsp?param=val; I ask this since it doesn't seem to work -- that parameter does not seem to get set. Also, at this point I'm in an https session and I'd like to transfer to unencrypted protocol -- how can I do that? Thanks in advance, Gil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Help needed in configuring tomcat 4.1.24
The xml parser complains about the comment inside the tag. I think you have to use grep when you shutdown as well in order to remove the WEB_PORT comment. /René -Original Message- From: Sarika Inamdar To: [EMAIL PROTECTED] Sent: 23-07-03 11:53 Subject: Help needed in configuring tomcat 4.1.24 Hi All, We need to start tomcat with a user-defined port. To enable the same , in server.xml, we give the following !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector !-- WEB_PORT --port=8080 minProcessors=5 maxProcessors=75 In our start script, we grep for WEB_PORT and replace the default port value with a user-defined port. With this modification, tomcat starts properly. But when I give shutdown.sh command to stop tomcat , I get the following parse exception : bash-2.03# ./shutdown.sh Using CATALINA_BASE: /export/spare/users/sinamdar/jakarta-tomcat-4.1.24 Using CATALINA_HOME: /export/spare/users/sinamdar/jakarta-tomcat-4.1.24 Using CATALINA_TMPDIR: /export/spare/users/sinamdar/jakarta-tomcat-4.1.24/temp Using JAVA_HOME: /export/spare/CSCOPerfE/tools/jdk Jul 23, 2003 3:12:03 PM org.apache.commons.digester.Digester fatalError SEVERE: Parse Fatal Error at line 93 column 5: Element type Connector must be followed by either attribute specifications, or /. org.xml.sax.SAXParseException: Element type Connector must be followed by either attribute specifications, or /. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unkno wn Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(U nknown Source) Is there anyway we can avoid this exception ? Any help in this regard would be useful. Thanks in Advance, Sarika - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Client authentication - no client certificate
Hi I have successfully setup Tomcat with SSL and client authentication, and I have successfully identified myself to the web application using a browser certificate. But when I access a port with client authentication enabled WITHOUT sending a certificate, I receive an error from Tomcat. I would like to present a nice web page to the user describing the error, but I cannot seem to find where to configure the error page. If it is configurable, can I configure it per request? Tomcat gives me the following stack trace (using Mozilla 1.4): Thread-14, WRITE: TLSv1 Handshake, length = 774 Thread-14, READ: TLSv1 Handshake, length = 141 *** Certificate chain *** Thread-14, SEND TLSv1 ALERT: fatal, description = bad_certificate Thread-14, WRITE: TLSv1 Alert, length = 2 Thread-14, called closeSocket() Thread-14, handling exception: javax.net.ssl.SSLHandshakeException: null cert chain With IE 6.0 I get the following stack trace: Thread-13, WRITE: SSLv3 Handshake, length = 774 Thread-13, READ: SSLv3 Alert, length = 2 Thread-13, RECV SSLv3 ALERT: warning, no_certificate SSL -- handshake alert: no_certificate Thread-13, handling exception: javax.net.ssl.SSLProtocolException: handshake ale rt: no_certificate Thread-13, SEND SSLv3 ALERT: fatal, description = unexpected_message Thread-13, WRITE: SSLv3 Alert, length = 2 Regards, René - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
