Another thing you could try is installing an http proxy to see what the headers 
look like for a good and bad request. Charles is a good proxy to use. This will 
help us diagnose the issue, assuming there's a difference between good and bad 
requests. If there isn't it's probably a bug in Chrome, or a difference in the 
way it interprets what tomcat is serving up.

Does the SOLO deployed version work every time?

-----Original Message-----
From: Chen Ding <[email protected]>
Sent: Tuesday, July 21, 2009 8:50 AM
To: P T Withington <[email protected]>
Cc: [email protected]
Subject: Re: [Laszlo-dev] Loading lzx file errors

As far as I can tell, tomcat did not generate any log. Before and after the 
problems occur, I did check the log. Nothing showed up. 

Chen Ding

On Tue, Jul 21, 2009 at 9:05 PM, P T Withington <[email protected]> wrote:
I wouldn't think so.  We only use browser switching to enable quirks (i.e, to 
handle the case where the browser does not comply with DOM2/CSS2).  Our default 
is to emit standards-compliant code, which should work in any compliant browser.

 The fact that the application works correctly sometimes also reenforces that 
it is not because of browser-switching on our part.

 I _do_ suspect that our server may emit cacheability information that may be 
misinterpreted by browsers that are very aggressive about caching.  I'm hardly 
the caching expert (I'm not sure anyone is :P), but I do think caching is a 
very tricky thing to get right.

 Finally, it would be really interesting to see the Tomcat logs for when the 
application does not appear. Possibly the compiler is just bombing (and the 
error not being caught) and emitting an empty app?


 On 2009-07-21, at 08:51EDT, Raju Bitter wrote:

I'm glad that you could solve your problem, Chen Ding.

 Tucker, could this be a problem with the user agent? In that case the page 
should never show, but maybe the problem is connected to it.
http://code.google.com/p/chromium/issues/detail?id=5985


 On Jul 21, 2009, at 1:34 PM, P T Withington wrote:



[The entire original message is not included]

Reply via email to