Re: [google-appengine] Stylesheet not being applied in Chome browser
We have an SDK update that resolves this issue on upload (I've also posted in a separate thread about this): http://code.google.com/p/googleappengine/downloads/detail?name=appengine-java-sdk-1.6.1.1.zip -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 10, 2012 at 3:08 PM, Amy Unruh amyu+gro...@google.com wrote: On Wed, Jan 11, 2012 at 6:58 AM, Ikai Lan (Google) ika...@google.comwrote: We think we know what's happening. This is something that is happening at app upload time. Can you try passing this parameter when using appcfg.sh? appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] To add to Ikai's workaround above: change your app's version name as well when you do the new --no_batch update. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 10, 2012 at 4:08 AM, Rik Scarborough rik...@gmail.comwrote: Not sure if this applies to this problem, but I've noticed that style type=text/css media=all@import default.css;/style no longer works in Chrome or later versions of IE. I had to use link rel=stylesheet href=default.css type=text/css media=all / ~Rik On Tue, Jan 10, 2012 at 5:02 AM, James Broberg jbrob...@gmail.comwrote: 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 extensioncss/extension mime-typetext/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
Re: [google-appengine] Stylesheet not being applied in Chome browser
Sweet! Please fast track an Eclipse Plugin update too. jon On Wed, Jan 11, 2012 at 5:22 PM, Ikai Lan (Google) ika...@google.comwrote: We have an SDK update that resolves this issue on upload (I've also posted in a separate thread about this): http://code.google.com/p/googleappengine/downloads/detail?name=appengine-java-sdk-1.6.1.1.zip -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 10, 2012 at 3:08 PM, Amy Unruh amyu+gro...@google.com wrote: On Wed, Jan 11, 2012 at 6:58 AM, Ikai Lan (Google) ika...@google.comwrote: We think we know what's happening. This is something that is happening at app upload time. Can you try passing this parameter when using appcfg.sh? appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] To add to Ikai's workaround above: change your app's version name as well when you do the new --no_batch update. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 10, 2012 at 4:08 AM, Rik Scarborough rik...@gmail.comwrote: Not sure if this applies to this problem, but I've noticed that style type=text/css media=all@import default.css;/style no longer works in Chrome or later versions of IE. I had to use link rel=stylesheet href=default.css type=text/css media=all / ~Rik On Tue, Jan 10, 2012 at 5:02 AM, James Broberg jbrob...@gmail.comwrote: 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 extensioncss/extension mime-typetext/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
Re: [google-appengine] Stylesheet not being applied in Chome browser
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 extensioncss/extension mime-typetext/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
Re: [google-appengine] Stylesheet not being applied in Chome browser
THIS IS EMBARRASING GOOGLE. 2012/1/10 James Broberg jbrob...@gmail.com 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 extensioncss/extension mime-typetext/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
Re: [google-appengine] Stylesheet not being applied in Chome browser
Not sure if this applies to this problem, but I've noticed that style type=text/css media=all@import default.css;/style no longer works in Chrome or later versions of IE. I had to use link rel=stylesheet href=default.css type=text/css media=all / ~Rik On Tue, Jan 10, 2012 at 5:02 AM, James Broberg jbrob...@gmail.com wrote: 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 extensioncss/extension mime-typetext/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
Re: [google-appengine] Stylesheet not being applied in Chome browser
We think we know what's happening. This is something that is happening at app upload time. Can you try passing this parameter when using appcfg.sh? appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 10, 2012 at 4:08 AM, Rik Scarborough rik...@gmail.com wrote: Not sure if this applies to this problem, but I've noticed that style type=text/css media=all@import default.css;/style no longer works in Chrome or later versions of IE. I had to use link rel=stylesheet href=default.css type=text/css media=all / ~Rik On Tue, Jan 10, 2012 at 5:02 AM, James Broberg jbrob...@gmail.com wrote: 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 extensioncss/extension mime-typetext/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
Re: [google-appengine] Stylesheet not being applied in Chome browser
On Wed, Jan 11, 2012 at 6:58 AM, Ikai Lan (Google) ika...@google.comwrote: We think we know what's happening. This is something that is happening at app upload time. Can you try passing this parameter when using appcfg.sh? appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] To add to Ikai's workaround above: change your app's version name as well when you do the new --no_batch update. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 10, 2012 at 4:08 AM, Rik Scarborough rik...@gmail.com wrote: Not sure if this applies to this problem, but I've noticed that style type=text/css media=all@import default.css;/style no longer works in Chrome or later versions of IE. I had to use link rel=stylesheet href=default.css type=text/css media=all / ~Rik On Tue, Jan 10, 2012 at 5:02 AM, James Broberg jbrob...@gmail.comwrote: 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 extensioncss/extension mime-typetext/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
Re: [google-appengine] Stylesheet not being applied in Chome browser
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
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 extensioncss/extension mime-typetext/css/mime-type /mime-mapping On Tue, Jan 10, 2012 at 6:27 AM, Ikai Lan (Google) ika...@google.comwrote: 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
RE: [google-appengine] Stylesheet not being applied in Chome browser
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 extensioncss/extension mime-typetext/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 http://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 http://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 http://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 mailto:google-appengine%2bunsubscr...@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 mailto:google-appengine%2bunsubscr...@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 mailto:google-appengine%2bunsubscr...@googlegroups.com
Re: [google-appengine] Stylesheet not being applied in Chome browser
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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
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.
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.comwrote: 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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
For those of you observing this problem, do you see it with Java apps? In particular, if anyone is seeing this with a python app, can you indicate that on this thread or the related issue http://code.google.com/p/googleappengine/issues/detail?id=6655 ? -Amy On Fri, Jan 6, 2012 at 1:54 PM, Ikai Lan (Google) ika...@google.com wrote: 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.comwrote: 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.
RE: [google-appengine] Stylesheet not being applied in Chome browser
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 http://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 http://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 mailto:google-appengine%2bunsubscr...@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 mailto:google-appengine%2bunsubscr...@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 mailto:google-appengine%2bunsubscr...@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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
I saw something similar in Chrome (didn't test other browsers). The response for the css was empty (in developer tools) but not when going directly to the URL. I cleared Chrome cache, ctrl-f5, ... I ended up doing the deployment twice every time (the css was empty on the first deploy and correct on the second). Every time again. The issue was gone after I increased the version number of my app. On Tue, Jan 3, 2012 at 10:33 PM, Ikai Lan (Google) ika...@google.comwrote: Try shift-refresh. If not, use Chrome's Developer Tools to see if the stylesheet is being loaded correctly. I suspect a cache issue. Click Resources to see if you are correctly downloading the stylesheet: http://code.google.com/chrome/devtools/docs/timeline.html -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 3, 2012 at 11:12 AM, Raffaele Magliocco ad...@rmzone.comwrote: Just trying to deploy a simple test app. Testing locally it works in IE, FF, and Chrome. But when deployed, my stylesheet is only being applied in IE and FF. Anyone seen something like this. I've looked on the forums but didn't find any help. No errors in the log either. -- 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. -- Pieter Coucke Onthoo BVBA http://www.onthoo.com/ - zamtam.com http://www.zamtam.com/ http://www.zamtam.co.uk/ -- 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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
I just had it again. It appears that the content-type is null which can explain why I can browse to the css URL and see the css but it isn't loaded in Chrome. Cache-Control: public, max-age=2678400 Content-Length: 13039 Content-Type: null Date: Wed, 04 Jan 2012 10:06:15 GMT ETag: KU-NKQ Expires: Sat, 04 Feb 2012 10:06:15 GMT Server: Google Frontend After increasing the version number the content-type is now Content-Type:text/css and the css loads again. On Wed, Jan 4, 2012 at 10:00 AM, Pieter Coucke pieter.cou...@onthoo.comwrote: I saw something similar in Chrome (didn't test other browsers). The response for the css was empty (in developer tools) but not when going directly to the URL. I cleared Chrome cache, ctrl-f5, ... I ended up doing the deployment twice every time (the css was empty on the first deploy and correct on the second). Every time again. The issue was gone after I increased the version number of my app. On Tue, Jan 3, 2012 at 10:33 PM, Ikai Lan (Google) ika...@google.comwrote: Try shift-refresh. If not, use Chrome's Developer Tools to see if the stylesheet is being loaded correctly. I suspect a cache issue. Click Resources to see if you are correctly downloading the stylesheet: http://code.google.com/chrome/devtools/docs/timeline.html -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 3, 2012 at 11:12 AM, Raffaele Magliocco ad...@rmzone.comwrote: Just trying to deploy a simple test app. Testing locally it works in IE, FF, and Chrome. But when deployed, my stylesheet is only being applied in IE and FF. Anyone seen something like this. I've looked on the forums but didn't find any help. No errors in the log either. -- 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. -- Pieter Coucke Onthoo BVBA http://www.onthoo.com/ - zamtam.com http://www.zamtam.com/ http://www.zamtam.co.uk/ -- Pieter Coucke Onthoo BVBA http://www.onthoo.com/ - zamtam.com http://www.zamtam.com/ http://www.zamtam.co.uk/ -- 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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
I always use the following method when uploading new application code. I have two versions of the code: dev and main main is the default version. I upload the new code to the dev version and test if the update is working by using the url http://dev.appname.appspot.com Then temporarily make dev the default version. Upload the code to main and make main the default. This method never failed for static content (css,js). I need to force reload shift-ctrl-R the page to ignore the browser cache content. If you apply a cache buster to your css link your users will see the updated css immediate. link type=text/css rel=stylesheet href=/css/style.css?ver=20120104 You need to change the string anytime you upload a new version. If you use source version control you can use the version number of the css file. -- 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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
I add an md5 hash of the app version to the css link, so the css is always fresh for a new version. You can not rely on your users to hit ctrl+refresh... On Wed, Jan 4, 2012 at 11:41 AM, djidjadji djidja...@gmail.com wrote: I always use the following method when uploading new application code. I have two versions of the code: dev and main main is the default version. I upload the new code to the dev version and test if the update is working by using the url http://dev.appname.appspot.com Then temporarily make dev the default version. Upload the code to main and make main the default. This method never failed for static content (css,js). I need to force reload shift-ctrl-R the page to ignore the browser cache content. If you apply a cache buster to your css link your users will see the updated css immediate. link type=text/css rel=stylesheet href=/css/style.css?ver=20120104 You need to change the string anytime you upload a new version. If you use source version control you can use the version number of the css file. -- 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. -- Pieter Coucke Onthoo BVBA http://www.onthoo.com/ - zamtam.com http://www.zamtam.com/ http://www.zamtam.co.uk/ -- 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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
There's also a chance this is a real Chrome issue. When talking to Google services, Chrome uses SPDY, not HTTP: http://en.wikipedia.org/wiki/SPDY I don't know if this applies to static assets deployed via the App Engine SDK. If it happens again, you can start debugging here in Chrome: chrome://net-internals/#eventsq=type:SPDY_SESSION%20is:active I suspect it might be a cache issue, but I don't want to rule out something weird going on with Chrome/SPDY/GAE. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Wed, Jan 4, 2012 at 9:20 AM, Pieter Coucke pieter.cou...@onthoo.comwrote: I add an md5 hash of the app version to the css link, so the css is always fresh for a new version. You can not rely on your users to hit ctrl+refresh... On Wed, Jan 4, 2012 at 11:41 AM, djidjadji djidja...@gmail.com wrote: I always use the following method when uploading new application code. I have two versions of the code: dev and main main is the default version. I upload the new code to the dev version and test if the update is working by using the url http://dev.appname.appspot.com Then temporarily make dev the default version. Upload the code to main and make main the default. This method never failed for static content (css,js). I need to force reload shift-ctrl-R the page to ignore the browser cache content. If you apply a cache buster to your css link your users will see the updated css immediate. link type=text/css rel=stylesheet href=/css/style.css?ver=20120104 You need to change the string anytime you upload a new version. If you use source version control you can use the version number of the css file. -- 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. -- Pieter Coucke Onthoo BVBA http://www.onthoo.com/ - zamtam.com http://www.zamtam.com/ http://www.zamtam.co.uk/ -- 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.
[google-appengine] Stylesheet not being applied in Chome browser
Just trying to deploy a simple test app. Testing locally it works in IE, FF, and Chrome. But when deployed, my stylesheet is only being applied in IE and FF. Anyone seen something like this. I've looked on the forums but didn't find any help. No errors in the log either. -- 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.
Re: [google-appengine] Stylesheet not being applied in Chome browser
Try shift-refresh. If not, use Chrome's Developer Tools to see if the stylesheet is being loaded correctly. I suspect a cache issue. Click Resources to see if you are correctly downloading the stylesheet: http://code.google.com/chrome/devtools/docs/timeline.html -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Tue, Jan 3, 2012 at 11:12 AM, Raffaele Magliocco ad...@rmzone.comwrote: Just trying to deploy a simple test app. Testing locally it works in IE, FF, and Chrome. But when deployed, my stylesheet is only being applied in IE and FF. Anyone seen something like this. I've looked on the forums but didn't find any help. No errors in the log either. -- 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.
