I set AxGzipOutput to off and the problem still appears (after ~10 requests) with AxKit 1.6.2 on MacOS X. The processing pipeline is kind of complicated, so i don't draw but instead try to describe it.
Emptying all cache is also sometimes needed when switching that off, but it'is probably ok in your case.
I hope this is understandable. If you got further questions just send me a Email (would it be useful if you could access the output of the two XSP-Pages above?).
Yes, it's understandable, but wow, you have many steps there, and the failure could happen at any time. Which part of the process creates the strings that are causing you trouble? If it's just one part, it would help locate the problem. Have you tried turning AxTraceIntermediate On? On a request where the data is wrong, you could get to see where the problem comes from by looking at the rotten string in each of the steps.
-- Robin Berjon <[EMAIL PROTECTED]> Research Engineer, Expway http://expway.fr/ 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
