You are kind of trolling. You aren't as yet effected by the bug, but are complaining about the response to the issue. "Simple issue" I kind of baited Brian the other day to ask why Numpy Savez couldn't get a "simple" fix and he gave a pretty good explanation of the complexities of a maintaining simple fixes, but more to this point, When you are working in a huge company on a product which is made up of other teams components there are no simple fixes. I am reminded of a bug that I worked on at Microsoft, Due to an issue in how packet headers supplemental data was escaped a certain combination of characters would cause the header to contain one character more than it was supposed to. This prevented these packets from passing over multicast through cisco equipment, and would result in a video glitch in the IPTV playback. At the Core the fix was easy. Don't put an extra character in the packet header. In reality a fix meant testing that the method used for escaping data would work with this changed in 136 products, 227 brands of and models of router/switch, and running MTBF testing on the OS after. Just the MTBF testing meant a fix would take a Month. But our "Simple" but worked out to be 3500 man hours and 75 days. Simple changes meaning drastically in Enterprise for Enterprise Class environments. From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Mos Sent: Monday, January 09, 2012 9:45 AM To: google-appengine@googlegroups.com Subject: Re: [google-appengine] Re: Fatal: Wrong mime-type in CSS responses Hello GAE-Team,
no news in 24h on this critical issue? I'm new to GAE and we will release our first application the next days. But this issue make me loose my confidence in GAE's reliability. I get doubt if Google App Engine was the right choice? As Jon mentioned: The issue is around on this list for more than two weeks. The issue breaks applications --> downtimes for more and more of your GAEs users And what I'm really wondering: It seems to be a simple fix on the GAE-Frontends. It shouldn't be such a complex thing, to evaluate why the response header sends a null mime-type and not the css mime-type for some application's *.css files? You have more then one test-case on this.... Your GAE guys are so smart and can't fix this one? Cheers Mos On Sun, Jan 8, 2012 at 11:15 PM, Amy Unruh <amyu+gro...@google.com <mailto:amyu%2bgro...@google.com> > wrote: Mos (and others), The issue is being actively investigated; we'll be sure to update this thread and the issue page as soon as there is more to report. Mos, you can go ahead and re-deploy if you want, as we have other test cases as this point. -Amy On Mon, Jan 9, 2012 at 5:00 AM, Mos <mosa...@googlemail.com> wrote: Hello Ikai, did you have the chance to evaluate on the issue? I sent you my broken test version / URL two days ago. I wanna redeploy in near future, but don't want to destroy "your test-case". Please give some feedback. Further I think we should put the issue on critical, because this bug breaks webpages and many people are affected: http://code.google.com/p/googleappengine/issues/detail?id=6655 Cheers Mos On Fri, Jan 6, 2012 at 12:26 PM, Mos <mosa...@googlemail.com> wrote: Hi Ikai, the problem occurs in all browsers (I tested Firefox, Chrome and IE). All browsers get a mime-type of null. Firefox is able to interpret the stylesheet nevertheless. IE and Chrome fail and the site is destroyed. Since yesterday I have a version of my application that still has the problem. I sent you the URL and the Beta-Login in a private email. I need to redepoy at the weekend, so please check it in the next hours. Greetings Mos On Thu, Jan 5, 2012 at 9:06 PM, Ikai Lan (Google) <ika...@google.com> wrote: Mos, what browser is this? I've seen some talk of this but it's passing and we can't seem to catch it in action. I need more data so I can hunt this down - URLs when this is failing. The reports I've seen are that this happens specifically to Chrome users. -- 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:37 AM, Mos <mosa...@googlemail.com> wrote: Just found the issue http://code.google.com/p/googleappengine/issues/detail?id=6655 It's three days old and describes a fatal error that seems to hit more and more people. No response from Google? On Thu, Jan 5, 2012 at 5:30 PM, Mos <mosa...@googlemail.com> wrote: My site is down currently, because GAE response CSS files without mime-type: REQUEST: GET /static/css/master.css HTTP/1.1 ... User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.25) Gecko/20111212 Firefox/3.6.25 Accept: text/css,*/*;q=0.1 ...... WRONG RESPONSE: HTTP/1.1 200 OK Etag: "sR7Bag" Date: Thu, 05 Jan 2012 16:22:34 GMT Expires: Thu, 05 Jan 2012 16:32:34 GMT Cache-Control: public, max-age=600 Content-Type: null Server: Google Frontend Content-Length: 37206 Does anybody else have the problem? -- 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 <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.
