In looking over the HTTP/1.1 spec, the header to set is 'Last-Modified'. In
the spec documentation, though, they state that there's 60 seconds of slop
allowed, in the event that the browser and server clocks are out of sync.
Still, they say that if the cached copy differs from the server copy by t
What kind of Date object are you using? There's the standard java.util.Date,
and then there's java.sql.Date passed into and returned by SQL queries. You may
need to convert from one to the other. The best way to do that is by using a
java.util.Calendar object.
Hope this helps.
- Roby
"Heijns, P
If you just need a test certificate for experimentation, check with Thawte:
theirs are free for application testing, and they don't trigger the
client-side 'Add a Certificate' dialog. Once you work out the bugs, try
Verisign or RSA for a production certificate.
- Roby
Sam Newman wrote:
> Tim Wr
I'm using JAAS to handle authentication. One of the things that you're able to
do is use pluggable authentication under Windows and Solaris (using the Sun
implementations) and Linux (with the IBM implementation), or authenticate
against a database (which is what I'm doing). The end result of the
a
You could try having the JSP set its modified time to 'now', using a
java.util.Calendar object. That should cause the cache on the browser to
retrieve an updated copy of the page. I don't recall how to do this in
JSP land, but servlets do it by implementing getLastModified(), derived
from HttpServ
Double-quotes. You want the value of the Java variable 'thePrice', not the
SQL text 'thePrice'.
Steve Ruby wrote:
> Mick Sullivan wrote:
> >
> > Hi,
> > Does anyone know why this statement WILL ADD a value to a record (Price)in a
> > database named parkingPrice:
> > Statement statement = connect
It doesn't look like this approach will work. JAAS=Java Authentication and
Authorization Service, a Sun Java extension
(http://java.sun.com/products/jaas).
For authentication, you construct a module for handling authentication services
for your application, and it has to implement
javax.security.
security issue. I
checked the supplied tomcat.policy file and added full security
permissions for the webapp directory and below, to no avail.
Was there a resolution found for this problem?
Thanks for your help.
Roby Gamboa
-
T
security issue. I
checked the supplied tomcat.policy file and added full security
permissions for the webapp directory and below, to no avail.
Was there a resolution found for this problem?
Thanks for your help.
Roby Gamboa
-
T