Single sign-on with Tomcat 3.21
The J2EE spec makes it clear that single sign-on for web-based applications should be supported (J2EE spec, section 3.4.1.1). The specification says: "It must be possible for one login session to span more than one application, allowing a user to log in once and access multiple applications." Is single sign-on supported by Tomcat 3.21? Frederic Kam-Thong - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: I don't want cached pages
This is what I use:
response.setHeader("Cache-Control", "no-cache");
response.setHeader("Pragma", "no-cache");
response.setDateHeader("Expires", System.currentTimeMillis());
response.setDateHeader("Last-Modified", System.currentTimeMillis());
The last line might be of help with browsers and proxies. (Then again, it
may not)
Hope it helps!
Frederic
-Original Message-
From: Hugo Lara [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 19, 2001 6:10 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: I don't want cached pages
I'm just one more guy with the same trouble: Tomcat is caching my pages.
I use a page that receives certain parameters and gives a result. And
everytime I made a request in the browser for that particular .jsp page, I
get the last version of that page served. It means that anyone entering my
site would see the last served paged with the results from the last visitor,
which is something terrible.
I've received some kind emails from the community suggesting me to include
the "Expires", "Pragma" and "Cache-control" (with the appropiate values) in
the header to avoid caching. This is not working, and that's because (and
I'm convinced of this) it's not a browser/proxy problem.
It is Tomcat that keeps the last version cached, and I'm sure of it because
it's enough to restart Tomcat to solve the problem.
Anyway, it will be crazy to restart Tomcat every time a visitor wants to
enter my site.
I've been reading the mailing and I've noticed there's a lot of people with
the same problem and no real solution.
I know that Amos Shapira and David S. Adress have been through the same.
If anyone has the solution to this problem please tell me, I need it very
badly.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Informix driver problems with Tomcat 3.2.1
Hi, List archives is broken... I get the following exception under Tomcat 3.2.1 but not under 3.2: Problem with registering the DataSource java.sql.SQLException: System or internal error java.lang.NullPointerException: at com.informix.util.IfxErrMsg.getLocSQLException(IfxErrMsg.java:439) at com.informix.jdbcx.IfxDataSource.init(IfxDataSource.java:79) at test.Register.registerDataSource(Register.java:69) at test.Register.main(Register.java:49) at test.InitServlet.init(InitServlet.java:21) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) at org.apache.tomcat.core.Handler.init(Handler.java:215) at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) at org.apache.tomcat.context.LoadOnStartupInterceptor.contextInit (LoadOnStartupInterceptor.java, Compiled Code) at org.apache.tomcat.core.ContextManager.initContext(ContextManager.java, Compiled Code) at org.apache.tomcat.core.ContextManager.init(ContextManager.java, Compiled Code) at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:195) at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235) - It's not a security problem. (I granted all permissions to all codebases) - Informix JDBC driver v2.2 Curiously, I don't get this exception when launching Tomcat 3.2.1 from IBM VisualAge for Java v3.5. How can I make sure that I am running Tomcat 3.2.1? Thanks! Frederic Kam-Thong _ Research Development, Invera Inc.
