I went ahead and wrote a Java helper class to convert from base 8 to base 10. This has resolved the problem. For those interested: private static String convert(String uid) { StringBuffer sb = new StringBuffer(); StringTokenizer octalString = new StringTokenizer(uid, "\\", false); Integer convert = new Integer(1); while(octalString.hasMoreTokens()) { sb.append((char)convert.parseInt(octalString.nextToken(), 8)); } return(sb.toString()); } I am still curious as to why Zope converts the data into base 8. Thanks for your response. -----Original Message----- From: Pavlos Christoforou [mailto:pavlos@gaaros.com] Sent: Thursday, March 16, 2000 10:59 PM To: Pearson, Brian Edward (GEA, 056278) Cc: 'zope@zope.org' Subject: Re: [Zope] Zope Cookie Handling On Thu, 16 Mar 2000, Pearson, Brian Edward (GEA, 056278) wrote:
Upon investigation of the value contained in the UID cookie, Zope returned the following:
\316\313\321\310\316\315\314\311\321\312\316\317\317\223\310\321\315\317\313
\316\317'
I am not sure what is going on but wouldn't it be generally safer if your java class converts the encrypted cookie in some ASCII text format first? I think that will solve your Zope problem too. Regards Pavlos _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )