Hi, Is there any progress on this? I am using a reverse proxy to tomcat. Everything is working beautifully except that about every tenth request under https, none of the images load on the page. Http works fine. Tomcat serves everything. I was hoping to put this customer on Cherokee in production.
One possible additional piece of info, I cannot seem to reproduce this in any browser on Linux. Maybe it is related to Windows? * Customer comments The account addresses screen seems to be the main one but yesterday it was also happening to me in the admin area. I'm on Windows 7 using the latest version of FireFox .... and it is also happening in IE 8 so I don't think it's a browser issue. * End Comments Tony Z On Mon, Feb 28, 2011 at 1:19 AM, Alvaro Lopez Ortega <[email protected]> wrote: > Hello James, > > Thank you for sharing your findings. Please log any additional information > you think might be useful to reproduce the problem in the bug reports (so we > keep every bit of information together). > > Fixing this problem is one of my highest priority tasks, so I'll try to get > it fixed as soon as possible. > > By the way, regarding the "Inherit Environment" question. I'd go for the (b) > - I don't think it has anything to do with the actual problem. > > Cheers! > > > On 27/02/2011, at 23:17, James wrote: > >> Thanks for the reply. >> >> I can absolutely consistently reproduce the problem. I don't see any >> specifics, however, regarding what you (and the other developers) >> would like to see in order to help fix this. >> >> I'm running a rather large dokuwiki environment on a server running >> Cherokee. When loading a wiki page that has one or two rather large >> (.png) diagrams, the graphics will remain "broken" until the second or >> third refresh of the page. >> >> It's worth noting that UNCHECKING the "Inherit Environment" checkbox >> in the Information Sources seems to have *VERY* slightly alleviated >> the problem...almost. ;) But repeated testing showed that either (a) >> it wasn't alleviated very much at all as the problem persisted, or (b) >> it was simply a placebo and the issue was not alleviated at all. :( >> >> Is there some specific information that I could gather that would >> assist in gathering the information needed to find the source of the >> problem? The only thing I figured may *possibly* help is an strace to >> see where things get stuck, but this may result in attempting to find >> a needle in a haystack. >> >> Thoughts / ideas greatly appreciated. >> >> -j >> >> >> On Mon, Feb 14, 2011 at 11:01, Alvaro Lopez Ortega <[email protected]> >> wrote: >>> Hello James, >>> >>> On 11/02/2011, at 19:47, James wrote: >>> >>>> Bumping a pretty old thread I started a while back. >>>> >>>> The issue is still occurring and seems to be getting worse. >>>> >>>> I'm not really sure where to start troubleshooting. Any ideas on how >>>> to deterministically ascertain whether the issue lies with Cherokee or >>>> Dokuwiki? >>>> >>>> This wiki is becoming a fairly mission-critical service and other >>>> users are starting to notice, particularly during image uploads, etc. >>> >>> There are a couple of bug reports where this issue is being tracked: >>> >>> http://bugs.cherokee-project.com/909 >>> http://bugs.cherokee-project.com/1105 >>> >>> Information on how to reproduce the issue is highly valuable to us. >>> Thanks! >>> >>> -- >>> Octality >>> http://www.octality.com/ > > -- > Octality > http://www.octality.com/ > > _______________________________________________ > Cherokee mailing list > [email protected] > http://lists.octality.com/listinfo/cherokee > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
