Tomcat4.0 - in process config with Apache
On http://jakarta.apache.org/tomcat/tomcat-3.3-doc/index.html, I found a reference how to setup an in process configuration of Tomcat 3.3 with Netscape and IIS. I wonder whether this is also possible for Apache 1.3.2x with Tomcat 4? If yes, how is it done and is this a robust setup. Thanks, Thomas -- Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Secure connection between Apache and Tomcat
Can I setup Apache and Tomcat in a way that Apache that the connection between Apache and Tomcat can be considered as secure, e.g. SSL In a guideline concerning the setup of Apache/Tomcat with SSL, I saw references to mod_jk parameters like JkExtractSSL, JkHTTPSIndicator,... What is the exact meaning of those parameters, do they extend a SSL session established by the Apache server to Tomcat? thanks, thomas -- Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen. Wenn Sie nicht der beabsichtigte Empfaenger sind, informieren Sie bitte sofort den Absender und loeschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der enthaltenenen Informationen ist nicht gestattet. The information contained in this message is confidential or protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorised copying of this message or unauthorised distribution of the information contained herein is prohibited. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
setAttribute behaviour when passing null as attribute
Hope, this wasn't discussed already (I browsed through the list but didn't
find it), if it was I apologize.
What is the expected result of calling setAttribute on an instance of
ServletRequest, if the attribute to be passed is null (i.e.
request.setAttribute(someName, null))?
I would expect that for the given name null is stored which would ensure
that a getAttribute call afterwards would return null as well.
However, the Tomcat implementation will leave the value unchanged:
--- code snippet from RequestImpl ---
Class org.apache.tomcat.core.RequestImpl.java line 614
public void setAttribute(String name, Object value) {
if(name!=null value!=null)
attributes.put(name, value);
}
--- end code snippet
Since other servlet container behave differently at least JRun does, namely
setting it to null, I wonder whether this is a bug in Tomcat?
I would argue that the expected behaviour is that getAttribute(name)
returns null, if a value for name was never set. In all other cases,
it should return exactly the value set with the last setAttribute call.
Any opinions on that?
best regards,
thomas
