@Jon, Notice that HTTP(304) call, that doesn't read response.headers, it only takes in what headers you give it. In this case it's none. Flip over to http.py line 77...there's your answer.
@Iceberg, As I've noted above, this is a web2py issue. I'm not going to have rocket remove headers that the application supplies. This goes back to the nanny web-server thing we discussed in another thread. @Everyone, So anyone wanna plugin that logging code I posted earlier and send me a log? Please. -tim On Jul 19, 10:34 pm, Iceberg <iceb...@21cn.com> wrote: > On Jul 20, 1:11am, Jonathan Lundell <jlund...@pobox.com> wrote: > > > > > > > On Jul 19, 2010, at 10:05 AM, Timbo wrote: > > > > It's defaulting to text/html since it's not actually sending a file. > > > This is a section of the HTTP spec that I missed. > > >http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.htmlsaysthat no > > > entity headers (Content-* should be sent in a 304 instance) > > > > I think I can have a patch by this evening. > > > > However, I've never seen this behavior before so I'll need for someone > > > to be able to test this to see if this is actually the cause of the > > > problem. Have we confirmed that the delay behavior happens in > > > different browsers? I only see chrome above. > > > I'm doubtful that the content-type is related to the delay; it seems more > > like a cosmetic issue. Still, since Chrome complains about it.... > > Tim, > > I think Chrome is more sensitive than others to complain incorrect > content-types. It is easy to see it in a Chrome (mine is 5.0.379.99 on > WinXP). Just start your local web2py server, then > visithttp://127.0.0.1:8000/welcome > and right-click at the background and choose the last item to pop-up a > "Developer Tools" window, then refresh the welcome page, now you can > see those Warnings such as "Resource interpreted as image but > transferred with MIME type text/html." > > It should not be harmful to satisfy chrome by Tim's coming patch. Even > it might not be relevant to the delay behavior. > > With respect to the delay behavior, I think it is cross browser, > albeit I don't have direct evidence. Most of my app's end users use > IE6/7/8, sometimes they complain some page take long time to load, but > usually a manually refresh (retry) can bypass the problem. :-/ > > Regards, > Iceberg
