> Has anyone applied this patch to their 2.0 JSDK yet? If so, were they any
> problems? Or, did you just replace the jar file and go on with your life (the
> answer I'm hoping for).
The answer you are looking for is the right one. Although, if you read what
it fixes you will notice that you really don't need it for 99.9999% cases
and even if you are hit by the bug it isn't a big deal cause all it means is
that the page won't be cached.
> Might as well add that JDK 118 is now out (security patch to 117).
If you are on Solaris, get the 1.2.1_03 production version. It is released
now and much better than 118. I don't understand why people haven't started
migrating to 1.2.x.
> Looks like I'm going to be fixing everything at once :(
It isn't that hard. I did it last night in under 30 minutes.
-jon
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
