A small caveat to the workaround posted on the issue: I happened to add a new css file to my application, and it is returning "Content-type: null" for the newly added css file, despite the explicit mime mapping in web.xml.
However, my existing css files still have the correct mimetype. On 10 January 2012 10:36, Brandon Wirtz <drak...@digerat.com> wrote: > To Ikai’s question about if this is happening in Python. I thought I had > seen it in Python, but upon inspection that was a Java Version of our app > that we hadn’t migrated to Python. So disregard my earlier mention that it > happens on Python as well. > > > > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Amy Unruh > Sent: Monday, January 09, 2012 3:14 PM > > > To: google-appengine@googlegroups.com > Subject: Re: [google-appengine] Stylesheet not being applied in Chome > browser > > > > For those affected, it looks like a workaround is to add the following to > your web.xml: > > > > <mime-mapping> > > <extension>css</extension> > > <mime-type>text/css</mime-type> > > </mime-mapping> > > > > On Tue, Jan 10, 2012 at 6:27 AM, Ikai Lan (Google) <ika...@google.com> > wrote: > > Can anyone confirm if they are seeing this for Python? We suspect this is > Java only and that this is happening during application upload. > > > -- > > Ikai Lan > Developer Programs Engineer, Google App Engine > > plus.ikailan.com | twitter.com/ikai > > > > On Thu, Jan 5, 2012 at 8:10 PM, Brandon Wirtz <drak...@digerat.com> wrote: > > It effects other assets. But yes Mime Type bothers Chrome more. Especially > on CSS. > > > > I believe it is an issue with Google “Front end” not GAE (just looking at > the ‘black box’) > > > > We have seen this on Python, and Java, with both static and non-static > assets. However unlike the behavior described in the bug, we were able to > solve the issue by specifying headers with expiration. However we found > that we had to get all of our semi-colons and spacing correct or “Front End” > would ignore them. The first time a URL was served it would not have a > specified Mime type, and after it would use the Detected mime type > regardless of the mime type we told it. (if we had any header specified with > a semicolor, space, or anything else not to it’s liking) > > sorry working remotely I don’t have a link to where it is still broken in > old code that we test from time to time, and I don’t have the forum post I > made that talks about getting the headers “right” > > > > > > From: google-appengine@googlegroups.com > [mailto:google-appengine@googlegroups.com] On Behalf Of Ikai Lan (Google) > Sent: Thursday, January 05, 2012 6:55 PM > To: google-appengine@googlegroups.com > > > Subject: Re: [google-appengine] Stylesheet not being applied in Chome > browser > > > > Okay. That's good information. We haven't been able to reproduce this yet, > but maybe we can find more information with some digging. > > > > I also wonder if it's also possible it's not limited to CSS files, it's just > that a null content-type doesn't impact browser rendering of any other > static asset. > > > -- > > Ikai Lan > Developer Programs Engineer, Google App Engine > > plus.ikailan.com | twitter.com/ikai > > > > On Thu, Jan 5, 2012 at 6:51 PM, Jon Stevens <latch...@gmail.com> wrote: > > No idea. We did a push of an app, css didn't look right. It seems limited to > css files for some reason. Maybe that'll be a clue for your engineers. > > > > jon > > > > On Thu, Jan 5, 2012 at 6:31 PM, Ikai Lan (Google) <ika...@google.com> wrote: > > It's sounding that way. Any chance you guys have noticed any details about > when this tends to happen? > > > -- > > Ikai Lan > Developer Programs Engineer, Google App Engine > > plus.ikailan.com | twitter.com/ikai > > > > On Thu, Jan 5, 2012 at 5:36 PM, Jon Stevens <latch...@gmail.com> wrote: > > Ikai, this is a real bug, not some browser cache issue. Your CDN is > returning Content-type: null headers, which is wrong. > > > > After posting a question to the google-appengine-java list and not getting > any response, I filed a bug 3 days ago that nobody has responded to. There > are 15 stars on it. > > > > http://code.google.com/p/googleappengine/issues/detail?id=6655 > > > > Please look into it. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/pHRtc8Qw1swJ. > > > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.