cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14348] - Caching problem with XSP, XSL and cocoon pseudo protocol
Date Fri, 25 Jul 2003 10:28:11 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14348>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14348

Caching problem with XSP, XSL and cocoon pseudo protocol

simon.huerlimann@access.unizh.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         OS/Version|Windows NT/2K               |All
           Platform|PC                          |All



------- Additional Comments From simon.huerlimann@access.unizh.ch  2003-07-25 10:28 -------
Old bug, but still a problem:-( 
 
Another workaround than removing the workingdir and restart seems to be to add some 
unused parameters to the request: 
 
1. Request foo 
2. Change bar 
3. Request foo -> cached, wrong result 
4. Request foo?a= -> newly generated, good result 
5. Request foo -> newly generated, good result 
6. Change bar 
7. Request foo -> cached, wrong result 
8. Request foo?a= -> cached, wrong result 
9. Request foo?b= -> newly generated, good result 
 
Unfortunatly, this just works *mostly*. Sometimes 5. still returns the old page, sometimes
9. 
doesn't work, but foo?a=&b= works.... 
 
I wasn't able to track down the exact behaviour. (If this bug wouldn't exist, I'd be faster

developing and would have time to investigate, but... :-)

Mime
View raw message