[appengine-java] Re: problem with Content-type: null with css files
I'm seeing this as well. It garbles up the whole page http://www.zivvit.com/css/main.css Any headway? I checked to make sure my file was encoded fine and everything. Not sure what's going on here... Seems like a bug in the static file distribution system. On Dec 24, 4:48 pm, jon stevens wrote: > Hey there, > > I've got an app up on GAE-J that when I request a .css file, I get back a > Content-Type: null, which is causing Chrome/Safari to not render the page > correctly. Any ideas why this would happen? Here is an example of what I > see in the Chrome Developer Tools -> Network -> Headers. I tried adding the > mime-extension to the web.xml and that didn't do anything. > > Request URL:http://appid.appspot.com/css/gen/main.css > Request Method:GET > Status Code:200 OK > > Request Headers > Accept:text/css,*/*;q=0.1 > Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 > Accept-Encoding:gzip,deflate,sdch > Accept-Language:en-US,en;q=0.8 > Authorization:Basic sldkjf > Cache-Control:max-age=0 > Connection:keep-alive > Host:appid.appspot.com > If-None-Match:"Cf2J0A" > Referer:http://appid.appspot.com/ > User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 > (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 > > Response Headers > Cache-Control:public, max-age=600 > Content-Length:112490 > Content-Type:null > Date:Sun, 25 Dec 2011 00:23:00 GMT > ETag:"NfQmpA" > Expires:Sun, 25 Dec 2011 00:33:00 GMT > Server:Google Frontend -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: problem with Content-type: null with css files
I got it working again by updating the version number in my appengine- web.xml and pushing the new version. Still have no idea what happened here. -J On Dec 24, 4:48 pm, jon stevens wrote: > Hey there, > > I've got an app up on GAE-J that when I request a .css file, I get back a > Content-Type: null, which is causing Chrome/Safari to not render the page > correctly. Any ideas why this would happen? Here is an example of what I > see in the Chrome Developer Tools -> Network -> Headers. I tried adding the > mime-extension to the web.xml and that didn't do anything. > > Request URL:http://appid.appspot.com/css/gen/main.css > Request Method:GET > Status Code:200 OK > > Request Headers > Accept:text/css,*/*;q=0.1 > Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 > Accept-Encoding:gzip,deflate,sdch > Accept-Language:en-US,en;q=0.8 > Authorization:Basic sldkjf > Cache-Control:max-age=0 > Connection:keep-alive > Host:appid.appspot.com > If-None-Match:"Cf2J0A" > Referer:http://appid.appspot.com/ > User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 > (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 > > Response Headers > Cache-Control:public, max-age=600 > Content-Length:112490 > Content-Type:null > Date:Sun, 25 Dec 2011 00:23:00 GMT > ETag:"NfQmpA" > Expires:Sun, 25 Dec 2011 00:33:00 GMT > Server:Google Frontend -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: problem with Content-type: null with css files
A FYI about alternating versions for deployment to production... Our build script names the version according data from SVN (GIT would be similar), as a working copy (name = data and time), revision (name=r123), or tag (name = tag name = our release version number). Then the uploaded versions in appengine Dashboard all show either with their release number (or revision, or date). You can have up to 10 of them uploaded in production, working against production data - but just one as the 'default'... On doing a new release/deploy to production (after previously testing on another appid in integration and qa), we test the basics via the specific version urlif everything looks fine we then make the new version the default. If something goes wrong, you can quickly sqitch back to any of the previous 9 releases you have made, usually the penultimate one off course. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
we had the same problem and it was solved by updating the css file (with a space) and pushing again (without an app version change). Appreciate any info you find on preventing this problem. It behaved as though it was a problem in GAE's caching of static files. On Dec 30, 2011, at 8:34 PM, jnamnath wrote: > I got it working again by updating the version number in my appengine- > web.xml and pushing the new version. Still have no idea what happened > here. > > -J > > On Dec 24, 4:48 pm, jon stevens wrote: >> Hey there, >> >> I've got an app up on GAE-J that when I request a .css file, I get back a >> Content-Type: null, which is causing Chrome/Safari to not render the page >> correctly. Any ideas why this would happen? Here is an example of what I >> see in the Chrome Developer Tools -> Network -> Headers. I tried adding the >> mime-extension to the web.xml and that didn't do anything. >> >> Request URL:http://appid.appspot.com/css/gen/main.css >> Request Method:GET >> Status Code:200 OK >> >> Request Headers >> Accept:text/css,*/*;q=0.1 >> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >> Accept-Encoding:gzip,deflate,sdch >> Accept-Language:en-US,en;q=0.8 >> Authorization:Basic sldkjf >> Cache-Control:max-age=0 >> Connection:keep-alive >> Host:appid.appspot.com >> If-None-Match:"Cf2J0A" >> Referer:http://appid.appspot.com/ >> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 >> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 >> >> Response Headers >> Cache-Control:public, max-age=600 >> Content-Length:112490 >> Content-Type:null >> Date:Sun, 25 Dec 2011 00:23:00 GMT >> ETag:"NfQmpA" >> Expires:Sun, 25 Dec 2011 00:33:00 GMT >> Server:Google Frontend > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
Well, it seems it isn't just me, so I just filed a ticket: http://code.google.com/p/googleappengine/issues/detail?id=6655 Please star it. jon On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan wrote: > we had the same problem and it was solved by updating the css file (with a > space) and pushing again (without an app version change). Appreciate any > info you find on preventing this problem. It behaved as though it was a > problem in GAE's caching of static files. > > > > > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: > >> I got it working again by updating the version number in my appengine- >> web.xml and pushing the new version. Still have no idea what happened >> here. >> >> -J >> >> On Dec 24, 4:48 pm, jon stevens wrote: >>> Hey there, >>> >>> I've got an app up on GAE-J that when I request a .css file, I get back a >>> Content-Type: null, which is causing Chrome/Safari to not render the page >>> correctly. Any ideas why this would happen? Here is an example of what I >>> see in the Chrome Developer Tools -> Network -> Headers. I tried adding the >>> mime-extension to the web.xml and that didn't do anything. >>> >>> Request URL:http://appid.appspot.com/css/gen/main.css >>> Request Method:GET >>> Status Code:200 OK >>> >>> Request Headers >>> Accept:text/css,*/*;q=0.1 >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >>> Accept-Encoding:gzip,deflate,sdch >>> Accept-Language:en-US,en;q=0.8 >>> Authorization:Basic sldkjf >>> Cache-Control:max-age=0 >>> Connection:keep-alive >>> Host:appid.appspot.com >>> If-None-Match:"Cf2J0A" >>> Referer:http://appid.appspot.com/ >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 >>> >>> Response Headers >>> Cache-Control:public, max-age=600 >>> Content-Length:112490 >>> Content-Type:null >>> Date:Sun, 25 Dec 2011 00:23:00 GMT >>> ETag:"NfQmpA" >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT >>> Server:Google Frontend >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To post to this group, send email to google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
For those affected, it looks like a workaround is to add the following to your web.xml: css text/css On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: > Well, it seems it isn't just me, so I just filed a ticket: > > http://code.google.com/p/googleappengine/issues/detail?id=6655 > > Please star it. > > jon > > > On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan wrote: > > we had the same problem and it was solved by updating the css file (with > a space) and pushing again (without an app version change). Appreciate any > info you find on preventing this problem. It behaved as though it was a > problem in GAE's caching of static files. > > > > > > > > > > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: > > > >> I got it working again by updating the version number in my appengine- > >> web.xml and pushing the new version. Still have no idea what happened > >> here. > >> > >> -J > >> > >> On Dec 24, 4:48 pm, jon stevens wrote: > >>> Hey there, > >>> > >>> I've got an app up on GAE-J that when I request a .css file, I get > back a > >>> Content-Type: null, which is causing Chrome/Safari to not render the > page > >>> correctly. Any ideas why this would happen? Here is an example of what > I > >>> see in the Chrome Developer Tools -> Network -> Headers. I tried > adding the > >>> mime-extension to the web.xml and that didn't do anything. > >>> > >>> Request URL:http://appid.appspot.com/css/gen/main.css > >>> Request Method:GET > >>> Status Code:200 OK > >>> > >>> Request Headers > >>> Accept:text/css,*/*;q=0.1 > >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 > >>> Accept-Encoding:gzip,deflate,sdch > >>> Accept-Language:en-US,en;q=0.8 > >>> Authorization:Basic sldkjf > >>> Cache-Control:max-age=0 > >>> Connection:keep-alive > >>> Host:appid.appspot.com > >>> If-None-Match:"Cf2J0A" > >>> Referer:http://appid.appspot.com/ > >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) > AppleWebKit/535.7 > >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 > >>> > >>> Response Headers > >>> Cache-Control:public, max-age=600 > >>> Content-Length:112490 > >>> Content-Type:null > >>> Date:Sun, 25 Dec 2011 00:23:00 GMT > >>> ETag:"NfQmpA" > >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT > >>> Server:Google Frontend > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups "Google App Engine for Java" group. > >> To post to this group, send email to > google-appengine-java@googlegroups.com. > >> To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > >> For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google > Groups "Google App Engine for Java" group. > > To post to this group, send email to > google-appengine-java@googlegroups.com. > > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
Just did that, redeployed and it didn't fix anything. Edited the part below to have .css (adding a period) and now the workaround to the workaround works. jon On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: > For those affected, it looks like a workaround is to add the following to > your web.xml: > > > css > text/css > > > On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: > >> Well, it seems it isn't just me, so I just filed a ticket: >> >> http://code.google.com/p/googleappengine/issues/detail?id=6655 >> >> Please star it. >> >> jon >> >> >> On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan wrote: >> > we had the same problem and it was solved by updating the css file >> (with a space) and pushing again (without an app version change). >> Appreciate any info you find on preventing this problem. It behaved as >> though it was a problem in GAE's caching of static files. >> > >> > >> > >> > >> > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: >> > >> >> I got it working again by updating the version number in my appengine- >> >> web.xml and pushing the new version. Still have no idea what happened >> >> here. >> >> >> >> -J >> >> >> >> On Dec 24, 4:48 pm, jon stevens wrote: >> >>> Hey there, >> >>> >> >>> I've got an app up on GAE-J that when I request a .css file, I get >> back a >> >>> Content-Type: null, which is causing Chrome/Safari to not render the >> page >> >>> correctly. Any ideas why this would happen? Here is an example of >> what I >> >>> see in the Chrome Developer Tools -> Network -> Headers. I tried >> adding the >> >>> mime-extension to the web.xml and that didn't do anything. >> >>> >> >>> Request URL:http://appid.appspot.com/css/gen/main.css >> >>> Request Method:GET >> >>> Status Code:200 OK >> >>> >> >>> Request Headers >> >>> Accept:text/css,*/*;q=0.1 >> >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >> >>> Accept-Encoding:gzip,deflate,sdch >> >>> Accept-Language:en-US,en;q=0.8 >> >>> Authorization:Basic sldkjf >> >>> Cache-Control:max-age=0 >> >>> Connection:keep-alive >> >>> Host:appid.appspot.com >> >>> If-None-Match:"Cf2J0A" >> >>> Referer:http://appid.appspot.com/ >> >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) >> AppleWebKit/535.7 >> >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 >> >>> >> >>> Response Headers >> >>> Cache-Control:public, max-age=600 >> >>> Content-Length:112490 >> >>> Content-Type:null >> >>> Date:Sun, 25 Dec 2011 00:23:00 GMT >> >>> ETag:"NfQmpA" >> >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT >> >>> Server:Google Frontend >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "Google App Engine for Java" group. >> >> To post to this group, send email to >> google-appengine-java@googlegroups.com. >> >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> >> >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Google App Engine for Java" group. >> > To post to this group, send email to >> google-appengine-java@googlegroups.com. >> > To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To post to this group, send email to >> google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
Are you all on the 1.6.1 SDK? Is someone experiencing this deploying with an older SDK? If someone has a deterministically reproducible case that you can share with us (project files and everything), it'd be very helpful for us to nail this bug. We aren't able to do this with our test apps (big apps, small apps). There's got to be some parameter that's different in your apps. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Mon, Jan 9, 2012 at 4:39 PM, Jon Stevens wrote: > Just did that, redeployed and it didn't fix anything. > > Edited the part below to have .css (adding a > period) and now the workaround to the workaround works. > > jon > > > On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: > >> For those affected, it looks like a workaround is to add the following to >> your web.xml: >> >> >> css >> text/css >> >> >> On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: >> >>> Well, it seems it isn't just me, so I just filed a ticket: >>> >>> http://code.google.com/p/googleappengine/issues/detail?id=6655 >>> >>> Please star it. >>> >>> jon >>> >>> >>> On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan >>> wrote: >>> > we had the same problem and it was solved by updating the css file >>> (with a space) and pushing again (without an app version change). >>> Appreciate any info you find on preventing this problem. It behaved as >>> though it was a problem in GAE's caching of static files. >>> > >>> > >>> > >>> > >>> > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: >>> > >>> >> I got it working again by updating the version number in my appengine- >>> >> web.xml and pushing the new version. Still have no idea what happened >>> >> here. >>> >> >>> >> -J >>> >> >>> >> On Dec 24, 4:48 pm, jon stevens wrote: >>> >>> Hey there, >>> >>> >>> >>> I've got an app up on GAE-J that when I request a .css file, I get >>> back a >>> >>> Content-Type: null, which is causing Chrome/Safari to not render the >>> page >>> >>> correctly. Any ideas why this would happen? Here is an example of >>> what I >>> >>> see in the Chrome Developer Tools -> Network -> Headers. I tried >>> adding the >>> >>> mime-extension to the web.xml and that didn't do anything. >>> >>> >>> >>> Request URL:http://appid.appspot.com/css/gen/main.css >>> >>> Request Method:GET >>> >>> Status Code:200 OK >>> >>> >>> >>> Request Headers >>> >>> Accept:text/css,*/*;q=0.1 >>> >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >>> >>> Accept-Encoding:gzip,deflate,sdch >>> >>> Accept-Language:en-US,en;q=0.8 >>> >>> Authorization:Basic sldkjf >>> >>> Cache-Control:max-age=0 >>> >>> Connection:keep-alive >>> >>> Host:appid.appspot.com >>> >>> If-None-Match:"Cf2J0A" >>> >>> Referer:http://appid.appspot.com/ >>> >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) >>> AppleWebKit/535.7 >>> >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 >>> >>> >>> >>> Response Headers >>> >>> Cache-Control:public, max-age=600 >>> >>> Content-Length:112490 >>> >>> Content-Type:null >>> >>> Date:Sun, 25 Dec 2011 00:23:00 GMT >>> >>> ETag:"NfQmpA" >>> >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT >>> >>> Server:Google Frontend >>> >> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> >> To post to this group, send email to >>> google-appengine-java@googlegroups.com. >>> >> To unsubscribe from this group, send email to >>> google-appengine-java+unsubscr...@googlegroups.com. >>> >> For more options, visit this group at >>> http://groups.google.com/group/google-appengine-java?hl=en. >>> >> >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> > To post to this group, send email to >>> google-appengine-java@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> google-appengine-java+unsubscr...@googlegroups.com. >>> > For more options, visit this group at >>> http://groups.google.com/group/google-appengine-java?hl=en. >>> > >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> To post to this group, send email to >>> google-appengine-java@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-appengine-java+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine-java?hl=en. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To post to this group, send email to >> google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> > > -- > You received this message because you are subscribed to the Google
Re: [appengine-java] Re: problem with Content-type: null with css files
Jon, FYI, this fix didn't work for me until I incremented the version number. Then it worked great. Cheers, Matt On Jan 9, 2012, at 4:39 PM, Jon Stevens wrote: > Just did that, redeployed and it didn't fix anything. > > Edited the part below to have .css (adding a period) > and now the workaround to the workaround works. > > jon > > > On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: > For those affected, it looks like a workaround is to add the following to > your web.xml: > > > css > text/css > > > On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: > Well, it seems it isn't just me, so I just filed a ticket: > > http://code.google.com/p/googleappengine/issues/detail?id=6655 > > Please star it. > > jon > > > On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan wrote: > > we had the same problem and it was solved by updating the css file (with a > > space) and pushing again (without an app version change). Appreciate any > > info you find on preventing this problem. It behaved as though it was a > > problem in GAE's caching of static files. > > > > > > > > > > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: > > > >> I got it working again by updating the version number in my appengine- > >> web.xml and pushing the new version. Still have no idea what happened > >> here. > >> > >> -J > >> > >> On Dec 24, 4:48 pm, jon stevens wrote: > >>> Hey there, > >>> > >>> I've got an app up on GAE-J that when I request a .css file, I get back a > >>> Content-Type: null, which is causing Chrome/Safari to not render the page > >>> correctly. Any ideas why this would happen? Here is an example of what I > >>> see in the Chrome Developer Tools -> Network -> Headers. I tried adding > >>> the > >>> mime-extension to the web.xml and that didn't do anything. > >>> > >>> Request URL:http://appid.appspot.com/css/gen/main.css > >>> Request Method:GET > >>> Status Code:200 OK > >>> > >>> Request Headers > >>> Accept:text/css,*/*;q=0.1 > >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 > >>> Accept-Encoding:gzip,deflate,sdch > >>> Accept-Language:en-US,en;q=0.8 > >>> Authorization:Basic sldkjf > >>> Cache-Control:max-age=0 > >>> Connection:keep-alive > >>> Host:appid.appspot.com > >>> If-None-Match:"Cf2J0A" > >>> Referer:http://appid.appspot.com/ > >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) > >>> AppleWebKit/535.7 > >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 > >>> > >>> Response Headers > >>> Cache-Control:public, max-age=600 > >>> Content-Length:112490 > >>> Content-Type:null > >>> Date:Sun, 25 Dec 2011 00:23:00 GMT > >>> ETag:"NfQmpA" > >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT > >>> Server:Google Frontend > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Google App Engine for Java" group. > >> To post to this group, send email to > >> google-appengine-java@googlegroups.com. > >> To unsubscribe from this group, send email to > >> google-appengine-java+unsubscr...@googlegroups.com. > >> For more options, visit this group at > >> http://groups.google.com/group/google-appengine-java?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine for Java" group. > > To post to this group, send email to google-appengine-java@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine-java+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/google-appengine-java?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubsc
Re: [appengine-java] Re: problem with Content-type: null with css files
It sounds like the data about this XML snippet is still inconclusive. - Jon Stevens reports that if you change the extension to .css, it works - Matt, in addition to using Jon's fix to the fix, you needed to increment the version to fix the broken mime-type So it's possible the XML snippet might be a red herring and it's something in the deployment/version incrementing mechanism that fixes something about the file being in a bad state. Does anyone else have anything to report? -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Mon, Jan 9, 2012 at 5:01 PM, Matthew Johnson wrote: > Jon, FYI, this fix didn't work for me until I incremented the version > number. Then it worked great. > > Cheers, > Matt > > > On Jan 9, 2012, at 4:39 PM, Jon Stevens wrote: > > Just did that, redeployed and it didn't fix anything. > > Edited the part below to have .css (adding a > period) and now the workaround to the workaround works. > > jon > > > On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: > >> For those affected, it looks like a workaround is to add the following to >> your web.xml: >> >> >> css >> text/css >> >> >> On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: >> >>> Well, it seems it isn't just me, so I just filed a ticket: >>> >>> http://code.google.com/p/googleappengine/issues/detail?id=6655 >>> >>> Please star it. >>> >>> jon >>> >>> >>> On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan >>> wrote: >>> > we had the same problem and it was solved by updating the css file >>> (with a space) and pushing again (without an app version change). >>> Appreciate any info you find on preventing this problem. It behaved as >>> though it was a problem in GAE's caching of static files. >>> > >>> > >>> > >>> > >>> > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: >>> > >>> >> I got it working again by updating the version number in my appengine- >>> >> web.xml and pushing the new version. Still have no idea what happened >>> >> here. >>> >> >>> >> -J >>> >> >>> >> On Dec 24, 4:48 pm, jon stevens wrote: >>> >>> Hey there, >>> >>> >>> >>> I've got an app up on GAE-J that when I request a .css file, I get >>> back a >>> >>> Content-Type: null, which is causing Chrome/Safari to not render the >>> page >>> >>> correctly. Any ideas why this would happen? Here is an example of >>> what I >>> >>> see in the Chrome Developer Tools -> Network -> Headers. I tried >>> adding the >>> >>> mime-extension to the web.xml and that didn't do anything. >>> >>> >>> >>> Request URL:http://appid.appspot.com/css/gen/main.css >>> >>> Request Method:GET >>> >>> Status Code:200 OK >>> >>> >>> >>> Request Headers >>> >>> Accept:text/css,*/*;q=0.1 >>> >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >>> >>> Accept-Encoding:gzip,deflate,sdch >>> >>> Accept-Language:en-US,en;q=0.8 >>> >>> Authorization:Basic sldkjf >>> >>> Cache-Control:max-age=0 >>> >>> Connection:keep-alive >>> >>> Host:appid.appspot.com >>> >>> If-None-Match:"Cf2J0A" >>> >>> Referer:http://appid.appspot.com/ >>> >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) >>> AppleWebKit/535.7 >>> >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 >>> >>> >>> >>> Response Headers >>> >>> Cache-Control:public, max-age=600 >>> >>> Content-Length:112490 >>> >>> Content-Type:null >>> >>> Date:Sun, 25 Dec 2011 00:23:00 GMT >>> >>> ETag:"NfQmpA" >>> >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT >>> >>> Server:Google Frontend >>> >> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> >> To post to this group, send email to >>> google-appengine-java@googlegroups.com. >>> >> To unsubscribe from this group, send email to >>> google-appengine-java+unsubscr...@googlegroups.com. >>> >> For more options, visit this group at >>> http://groups.google.com/group/google-appengine-java?hl=en. >>> >> >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> > To post to this group, send email to >>> google-appengine-java@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> google-appengine-java+unsubscr...@googlegroups.com. >>> > For more options, visit this group at >>> http://groups.google.com/group/google-appengine-java?hl=en. >>> > >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> To post to this group, send email to >>> google-appengine-java@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-appengine-java+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine-java?hl=en. >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To post to this group, send email to >> google-appengine-java@googlegroups.com.
Re: [appengine-java] Re: problem with Content-type: null with css files
I have no idea how your internal systems work, but I'd look into the code which sets the Content-Type header and see what could possibly set it to null or not set it at all and then work back from there. Some more data points for reproduction? My css file is fairly large since I have one file for my entire site: ~143k The file is nested in the war file. /war/css/main.css The file is generated via a bunch of .less files and compiled with lessc. jon On Mon, Jan 9, 2012 at 5:20 PM, Ikai Lan (Google) wrote: > It sounds like the data about this XML snippet is still inconclusive. > > - Jon Stevens reports that if you change the extension to .css, it works > - Matt, in addition to using Jon's fix to the fix, you needed to increment > the version to fix the broken mime-type > > So it's possible the XML snippet might be a red herring and it's something > in the deployment/version incrementing mechanism that fixes something about > the file being in a bad state. > > Does anyone else have anything to report? > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > plus.ikailan.com | twitter.com/ikai > > > > On Mon, Jan 9, 2012 at 5:01 PM, Matthew Johnson > wrote: > >> Jon, FYI, this fix didn't work for me until I incremented the version >> number. Then it worked great. >> >> Cheers, >> Matt >> >> >> On Jan 9, 2012, at 4:39 PM, Jon Stevens wrote: >> >> Just did that, redeployed and it didn't fix anything. >> >> Edited the part below to have .css (adding a >> period) and now the workaround to the workaround works. >> >> jon >> >> >> On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: >> >>> For those affected, it looks like a workaround is to add the following >>> to your web.xml: >>> >>> >>> css >>> text/css >>> >>> >>> On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: >>> Well, it seems it isn't just me, so I just filed a ticket: http://code.google.com/p/googleappengine/issues/detail?id=6655 Please star it. jon On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan wrote: > we had the same problem and it was solved by updating the css file (with a space) and pushing again (without an app version change). Appreciate any info you find on preventing this problem. It behaved as though it was a problem in GAE's caching of static files. > > > > > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: > >> I got it working again by updating the version number in my appengine- >> web.xml and pushing the new version. Still have no idea what happened >> here. >> >> -J >> >> On Dec 24, 4:48 pm, jon stevens wrote: >>> Hey there, >>> >>> I've got an app up on GAE-J that when I request a .css file, I get back a >>> Content-Type: null, which is causing Chrome/Safari to not render the page >>> correctly. Any ideas why this would happen? Here is an example of what I >>> see in the Chrome Developer Tools -> Network -> Headers. I tried adding the >>> mime-extension to the web.xml and that didn't do anything. >>> >>> Request URL:http://appid.appspot.com/css/gen/main.css >>> Request Method:GET >>> Status Code:200 OK >>> >>> Request Headers >>> Accept:text/css,*/*;q=0.1 >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >>> Accept-Encoding:gzip,deflate,sdch >>> Accept-Language:en-US,en;q=0.8 >>> Authorization:Basic sldkjf >>> Cache-Control:max-age=0 >>> Connection:keep-alive >>> Host:appid.appspot.com >>> If-None-Match:"Cf2J0A" >>> Referer:http://appid.appspot.com/ >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 >>> >>> Response Headers >>> Cache-Control:public, max-age=600 >>> Content-Length:112490 >>> Content-Type:null >>> Date:Sun, 25 Dec 2011 00:23:00 GMT >>> ETag:"NfQmpA" >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT >>> Server:Google Frontend >> >> -- >> You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. >> To post to this group, send email to google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/g
Re: [appengine-java] Re: problem with Content-type: null with css files
Ikai, I'm using GAP SDK 1.6.1, and so far, I'm the only dev on my team who's experienced this. Sorry I wasn't clear in my earlier reply to Jon. I did NOT need to use Jon's fix; my mime-mapping entry (seemed to) work fine without the period, but only AFTER I incremented the version number. I pushed twice to the same version number after adding the mime-mapping entry with no results. I just removed the xml entry and deployed to the working version number. The mime-type problem resurfaces without the entry, so I don't think it's a red herring. Here's a point of interest: we use a CSS build process, and the symptom first occurred after a fresh build and a deploy to a new version number. Thinking it was a syntax related error, I pulled the content from the default version of my app and pasted it into the css file in question. This *fixed the problem*. I just confirmed that with my freshly incremented build I can fix the css mime-type issue by copying in css content from the default version, without the mime-mapping entry. Once I use the newer css, the problem resurfaces. Summary: -Mime-mapping entry didn't work until I updated the version number. -After fixing with the new version and Mime-mapping entry, removing the mime-mapping entry reintroduced the problem. -I can also fix the content-type by copying content from my default app's version of the file into this version, and pushing that to the same version (without the mime-mapping entry) Hope these (strange) details help out a bit. Cheers, Matt On Jan 9, 2012, at 5:20 PM, Ikai Lan (Google) wrote: > It sounds like the data about this XML snippet is still inconclusive. > > - Jon Stevens reports that if you change the extension to .css, it works > - Matt, in addition to using Jon's fix to the fix, you needed to increment > the version to fix the broken mime-type > > So it's possible the XML snippet might be a red herring and it's something in > the deployment/version incrementing mechanism that fixes something about the > file being in a bad state. > > Does anyone else have anything to report? > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > plus.ikailan.com | twitter.com/ikai > > > > On Mon, Jan 9, 2012 at 5:01 PM, Matthew Johnson > wrote: > Jon, FYI, this fix didn't work for me until I incremented the version number. > Then it worked great. > > Cheers, > Matt > > > On Jan 9, 2012, at 4:39 PM, Jon Stevens wrote: > >> Just did that, redeployed and it didn't fix anything. >> >> Edited the part below to have .css (adding a period) >> and now the workaround to the workaround works. >> >> jon >> >> >> On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: >> For those affected, it looks like a workaround is to add the following to >> your web.xml: >> >> >> css >> text/css >> >> >> On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: >> Well, it seems it isn't just me, so I just filed a ticket: >> >> http://code.google.com/p/googleappengine/issues/detail?id=6655 >> >> Please star it. >> >> jon >> >> >> On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan wrote: >> > we had the same problem and it was solved by updating the css file (with a >> > space) and pushing again (without an app version change). Appreciate any >> > info you find on preventing this problem. It behaved as though it was a >> > problem in GAE's caching of static files. >> > >> > >> > >> > >> > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: >> > >> >> I got it working again by updating the version number in my appengine- >> >> web.xml and pushing the new version. Still have no idea what happened >> >> here. >> >> >> >> -J >> >> >> >> On Dec 24, 4:48 pm, jon stevens wrote: >> >>> Hey there, >> >>> >> >>> I've got an app up on GAE-J that when I request a .css file, I get back a >> >>> Content-Type: null, which is causing Chrome/Safari to not render the page >> >>> correctly. Any ideas why this would happen? Here is an example of what I >> >>> see in the Chrome Developer Tools -> Network -> Headers. I tried adding >> >>> the >> >>> mime-extension to the web.xml and that didn't do anything. >> >>> >> >>> Request URL:http://appid.appspot.com/css/gen/main.css >> >>> Request Method:GET >> >>> Status Code:200 OK >> >>> >> >>> Request Headers >> >>> Accept:text/css,*/*;q=0.1 >> >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >> >>> Accept-Encoding:gzip,deflate,sdch >> >>> Accept-Language:en-US,en;q=0.8 >> >>> Authorization:Basic sldkjf >> >>> Cache-Control:max-age=0 >> >>> Connection:keep-alive >> >>> Host:appid.appspot.com >> >>> If-None-Match:"Cf2J0A" >> >>> Referer:http://appid.appspot.com/ >> >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) >> >>> AppleWebKit/535.7 >> >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 >> >>> >> >>> Response Headers >> >>> Cache-Control:public, max-age=600 >> >>> Content-Length:112490 >> >>> Content-Type:null >> >>> Date:Sun, 25 Dec 2011 00:23:00 GM
Re: [appengine-java] Re: problem with Content-type: null with css files
> If someone has a deterministically reproducible case that you can share with
> us (project files and everything), it'd be very helpful for us to nail this
> bug. We aren't able to do this with our test apps (big apps, small apps).
> There's got to be some parameter that's different in your apps.
I had the same problem and realized I can induce/eliminate the error
just by altering a comment (the first lines in the file -- not sure
about elsewhere).
test 1 - This fails:
/*test
*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
test 2 - This succeeds:
/*test
*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
test 3 - this fails:
/*test*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
test 4 - this succeeds:
/*test*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
test 5 - this succeeds
/*test
*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
(when combined with web.xml):
.css
text/css
NOTE: It's more complicated that I depict here as if I remove the
web.xml workaround for test 5 it still works. But then if I add
another space between the comment and first html rule, it fails again.
Anyway, just changing the spacing around the initial comment will
result in the mime type being set or not.
NOTE 2: I verified my css file was w3c valid but I have not posted the
whole thing. The only change was spacing around the initial
comment...
NOTE3: AE 1.6.1
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
I just ran into it after a push, right after everything reset and with the css mime-type workaround in place. jon On Mon, Jan 9, 2012 at 6:19 PM, Matthew Johnson wrote: > Ikai, > > I'm using GAP SDK 1.6.1, and so far, I'm the only dev on my team who's > experienced this. > > Sorry I wasn't clear in my earlier reply to Jon. I did NOT need to use > Jon's fix; my mime-mapping entry (seemed to) work fine without the period, > but only AFTER I incremented the version number. I pushed twice to the same > version number after adding the mime-mapping entry with no results. > > I just removed the xml entry and deployed to the working version number. > The mime-type problem resurfaces without the entry, so I don't think it's a > red herring. > > > Here's a point of interest: we use a CSS build process, and the symptom > first occurred after a fresh build and a deploy to a new version number. > Thinking it was a syntax related error, I pulled the content from the > default version of my app and pasted it into the css file in question. This > *fixed the problem*. I just confirmed that with my freshly incremented > build I can fix the css mime-type issue by copying in css content from the > default version, without the mime-mapping entry. Once I use the newer css, > the problem resurfaces. > > Summary: > -Mime-mapping entry didn't work until I updated the version number. > -After fixing with the new version and Mime-mapping entry, removing the > mime-mapping entry reintroduced the problem. > -I can also fix the content-type by copying content from my default > app's version of the file into this version, and pushing that to the same > version (without the mime-mapping entry) > > Hope these (strange) details help out a bit. > > Cheers, > Matt > > On Jan 9, 2012, at 5:20 PM, Ikai Lan (Google) wrote: > > It sounds like the data about this XML snippet is still inconclusive. > > - Jon Stevens reports that if you change the extension to .css, it works > - Matt, in addition to using Jon's fix to the fix, you needed to increment > the version to fix the broken mime-type > > So it's possible the XML snippet might be a red herring and it's something > in the deployment/version incrementing mechanism that fixes something about > the file being in a bad state. > > Does anyone else have anything to report? > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > plus.ikailan.com | twitter.com/ikai > > > > On Mon, Jan 9, 2012 at 5:01 PM, Matthew Johnson > wrote: > >> Jon, FYI, this fix didn't work for me until I incremented the version >> number. Then it worked great. >> >> Cheers, >> Matt >> >> >> On Jan 9, 2012, at 4:39 PM, Jon Stevens wrote: >> >> Just did that, redeployed and it didn't fix anything. >> >> Edited the part below to have .css (adding a >> period) and now the workaround to the workaround works. >> >> jon >> >> >> On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: >> >>> For those affected, it looks like a workaround is to add the following >>> to your web.xml: >>> >>> >>> css >>> text/css >>> >>> >>> On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: >>> Well, it seems it isn't just me, so I just filed a ticket: http://code.google.com/p/googleappengine/issues/detail?id=6655 Please star it. jon On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan wrote: > we had the same problem and it was solved by updating the css file (with a space) and pushing again (without an app version change). Appreciate any info you find on preventing this problem. It behaved as though it was a problem in GAE's caching of static files. > > > > > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: > >> I got it working again by updating the version number in my appengine- >> web.xml and pushing the new version. Still have no idea what happened >> here. >> >> -J >> >> On Dec 24, 4:48 pm, jon stevens wrote: >>> Hey there, >>> >>> I've got an app up on GAE-J that when I request a .css file, I get back a >>> Content-Type: null, which is causing Chrome/Safari to not render the page >>> correctly. Any ideas why this would happen? Here is an example of what I >>> see in the Chrome Developer Tools -> Network -> Headers. I tried adding the >>> mime-extension to the web.xml and that didn't do anything. >>> >>> Request URL:http://appid.appspot.com/css/gen/main.css >>> Request Method:GET >>> Status Code:200 OK >>> >>> Request Headers >>> Accept:text/css,*/*;q=0.1 >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >>> Accept-Encoding:gzip,deflate,sdch >>> Accept-Language:en-US,en;q=0.8 >>> Authorization:Basic sldkjf >>> Cache-Control:max-age=0 >>> Connection:keep-alive >>> Host:appid.appspot.com >>> If-None-Match:"Cf2J0A" >>> Referer:http://appid.appspot.com/ >>>
Re: [appengine-java] Re: problem with Content-type: null with css files
Please I can't complete my application till today???
Sent from my BlackBerry® Smartphone, from Etisalat. Enjoy high speed internet
service with Etisalat easy net, available at all our experience centres
-Original Message-
From: Shawn Brown
Sender: google-appengine-java@googlegroups.com
Date: Tue, 10 Jan 2012 16:08:39
To:
Reply-To: google-appengine-java@googlegroups.com
Cc:
Subject: Re: [appengine-java] Re: problem with Content-type: null with css files
> If someone has a deterministically reproducible case that you can share with
> us (project files and everything), it'd be very helpful for us to nail this
> bug. We aren't able to do this with our test apps (big apps, small apps).
> There's got to be some parameter that's different in your apps.
I had the same problem and realized I can induce/eliminate the error
just by altering a comment (the first lines in the file -- not sure
about elsewhere).
test 1 - This fails:
/*test
*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
test 2 - This succeeds:
/*test
*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
test 3 - this fails:
/*test*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
test 4 - this succeeds:
/*test*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
test 5 - this succeeds
/*test
*/
html,body,h1,h2,h3,h4,h5,h6,p,ol,ul,li,pre,code,address,variable,form,fieldset,blockquote
{
padding: 0;
margin: 0;
font-size: 100%;
font-weight: normal;
}
(when combined with web.xml):
.css
text/css
NOTE: It's more complicated that I depict here as if I remove the
web.xml workaround for test 5 it still works. But then if I add
another space between the comment and first html rule, it fails again.
Anyway, just changing the spacing around the initial comment will
result in the mime type being set or not.
NOTE 2: I verified my css file was w3c valid but I have not posted the
whole thing. The only change was spacing around the initial
comment...
NOTE3: AE 1.6.1
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
Ikai, I sent you my testcase some days ago (it's still broken). Can't you use it? Didn't get any feedback from you? I'm pretty sure: - It's a SDK 1.6.1 issue (didn't get it before, but got it now from time to time when doing deployments) - It seems to be Java only - It seems to be a race-condition Is your code for determine the mime-type of deployed somewhere available. I'm sure a lot of people would like to see it and helping out. ;) My strong statement is on the other thread: http://groups.google.com/group/google-appengine/msg/ba3ae8475e555c0f On Tue, Jan 10, 2012 at 1:58 AM, Ikai Lan (Google) wrote: > Are you all on the 1.6.1 SDK? Is someone experiencing this deploying with > an older SDK? > > If someone has a deterministically reproducible case that you can share > with us (project files and everything), it'd be very helpful for us to nail > this bug. We aren't able to do this with our test apps (big apps, small > apps). There's got to be some parameter that's different in your apps. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > plus.ikailan.com | twitter.com/ikai > > > > On Mon, Jan 9, 2012 at 4:39 PM, Jon Stevens wrote: > >> Just did that, redeployed and it didn't fix anything. >> >> Edited the part below to have .css (adding a >> period) and now the workaround to the workaround works. >> >> jon >> >> >> On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: >> >>> For those affected, it looks like a workaround is to add the following >>> to your web.xml: >>> >>> >>> css >>> text/css >>> >>> >>> On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: >>> Well, it seems it isn't just me, so I just filed a ticket: http://code.google.com/p/googleappengine/issues/detail?id=6655 Please star it. jon On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan wrote: > we had the same problem and it was solved by updating the css file (with a space) and pushing again (without an app version change). Appreciate any info you find on preventing this problem. It behaved as though it was a problem in GAE's caching of static files. > > > > > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: > >> I got it working again by updating the version number in my appengine- >> web.xml and pushing the new version. Still have no idea what happened >> here. >> >> -J >> >> On Dec 24, 4:48 pm, jon stevens wrote: >>> Hey there, >>> >>> I've got an app up on GAE-J that when I request a .css file, I get back a >>> Content-Type: null, which is causing Chrome/Safari to not render the page >>> correctly. Any ideas why this would happen? Here is an example of what I >>> see in the Chrome Developer Tools -> Network -> Headers. I tried adding the >>> mime-extension to the web.xml and that didn't do anything. >>> >>> Request URL:http://appid.appspot.com/css/gen/main.css >>> Request Method:GET >>> Status Code:200 OK >>> >>> Request Headers >>> Accept:text/css,*/*;q=0.1 >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 >>> Accept-Encoding:gzip,deflate,sdch >>> Accept-Language:en-US,en;q=0.8 >>> Authorization:Basic sldkjf >>> Cache-Control:max-age=0 >>> Connection:keep-alive >>> Host:appid.appspot.com >>> If-None-Match:"Cf2J0A" >>> Referer:http://appid.appspot.com/ >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.7 >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 >>> >>> Response Headers >>> Cache-Control:public, max-age=600 >>> Content-Length:112490 >>> Content-Type:null >>> Date:Sun, 25 Dec 2011 00:23:00 GMT >>> ETag:"NfQmpA" >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT >>> Server:Google Frontend >> >> -- >> You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. >> To post to this group, send email to google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, sen
Re: [appengine-java] Re: problem with Content-type: null with css files
Just to update this thread with info from another thread: We think we know what's happening. This is something that is happening at app upload time. Can you try setting a new version name for your app, then passing the --no_batch option when using appcfg.sh? appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] On Tue, Jan 10, 2012 at 9:38 PM, Mos wrote: > Ikai, I sent you my testcase some days ago (it's still broken). Can't you > use it? Didn't get any feedback from you? > > I'm pretty sure: > - It's a SDK 1.6.1 issue (didn't get it before, but got it now from time > to time when doing deployments) > - It seems to be Java only > - It seems to be a race-condition > > Is your code for determine the mime-type of deployed somewhere available. > I'm sure a lot of people > would like to see it and helping out. ;) > > My strong statement is on the other thread: > > http://groups.google.com/group/google-appengine/msg/ba3ae8475e555c0f > > > > On Tue, Jan 10, 2012 at 1:58 AM, Ikai Lan (Google) wrote: > >> Are you all on the 1.6.1 SDK? Is someone experiencing this deploying with >> an older SDK? >> >> If someone has a deterministically reproducible case that you can share >> with us (project files and everything), it'd be very helpful for us to nail >> this bug. We aren't able to do this with our test apps (big apps, small >> apps). There's got to be some parameter that's different in your apps. >> >> -- >> Ikai Lan >> Developer Programs Engineer, Google App Engine >> plus.ikailan.com | twitter.com/ikai >> >> >> >> On Mon, Jan 9, 2012 at 4:39 PM, Jon Stevens wrote: >> >>> Just did that, redeployed and it didn't fix anything. >>> >>> Edited the part below to have .css (adding a >>> period) and now the workaround to the workaround works. >>> >>> jon >>> >>> >>> On Mon, Jan 9, 2012 at 3:16 PM, Amy Unruh wrote: >>> For those affected, it looks like a workaround is to add the following to your web.xml: css text/css On Mon, Jan 2, 2012 at 3:19 PM, Jon Stevens wrote: > Well, it seems it isn't just me, so I just filed a ticket: > > http://code.google.com/p/googleappengine/issues/detail?id=6655 > > Please star it. > > jon > > > On Sun, Jan 1, 2012 at 8:13 PM, Carter Maslan > wrote: > > we had the same problem and it was solved by updating the css file > (with a space) and pushing again (without an app version change). > Appreciate any info you find on preventing this problem. It behaved as > though it was a problem in GAE's caching of static files. > > > > > > > > > > On Dec 30, 2011, at 8:34 PM, jnamnath wrote: > > > >> I got it working again by updating the version number in my > appengine- > >> web.xml and pushing the new version. Still have no idea what > happened > >> here. > >> > >> -J > >> > >> On Dec 24, 4:48 pm, jon stevens wrote: > >>> Hey there, > >>> > >>> I've got an app up on GAE-J that when I request a .css file, I get > back a > >>> Content-Type: null, which is causing Chrome/Safari to not render > the page > >>> correctly. Any ideas why this would happen? Here is an example of > what I > >>> see in the Chrome Developer Tools -> Network -> Headers. I tried > adding the > >>> mime-extension to the web.xml and that didn't do anything. > >>> > >>> Request URL:http://appid.appspot.com/css/gen/main.css > >>> Request Method:GET > >>> Status Code:200 OK > >>> > >>> Request Headers > >>> Accept:text/css,*/*;q=0.1 > >>> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3 > >>> Accept-Encoding:gzip,deflate,sdch > >>> Accept-Language:en-US,en;q=0.8 > >>> Authorization:Basic sldkjf > >>> Cache-Control:max-age=0 > >>> Connection:keep-alive > >>> Host:appid.appspot.com > >>> If-None-Match:"Cf2J0A" > >>> Referer:http://appid.appspot.com/ > >>> User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) > AppleWebKit/535.7 > >>> (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 > >>> > >>> Response Headers > >>> Cache-Control:public, max-age=600 > >>> Content-Length:112490 > >>> Content-Type:null > >>> Date:Sun, 25 Dec 2011 00:23:00 GMT > >>> ETag:"NfQmpA" > >>> Expires:Sun, 25 Dec 2011 00:33:00 GMT > >>> Server:Google Frontend > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups "Google App Engine for Java" group. > >> To post to this group, send email to > google-appengine-java@googlegroups.com. > >> To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > >> For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google > Groups
Re: [appengine-java] Re: problem with Content-type: null with css files
> We think we know what's happening. This is something that is happening at > app upload time. Can you try setting a new version name for your app, then > passing the --no_batch option when using appcfg.sh? > > appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] Seems to solve it. I can't reproduce the error as I did by just modifying the spaces in comments in the css file anymore. Shawn -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
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:38 PM, Shawn Brown wrote: > > We think we know what's happening. This is something that is happening at > > app upload time. Can you try setting a new version name for your app, > then > > passing the --no_batch option when using appcfg.sh? > > > > appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] > > > Seems to solve it. I can't reproduce the error as I did by just > modifying the spaces in comments in the css file anymore. > > Shawn > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
Ikai - Our site was unusable for 30 minutes while we quickly downloaded the 1.6.1.1 fix and redeployed with the new SDK. We could have deployed in two phases with a different version so that we could have discovered the bug prior to being live. Is it best practice to alternate between versions with *each and every* deployment in order to catch deployment-specific bugs? Or do you think your deployment-related testing is sufficiently good that we can rely on the integrity of deployment? thanks, Carter On Wed, Jan 11, 2012 at 5:22 PM, Ikai Lan (Google) wrote: > 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:38 PM, Shawn Brown > wrote: > >> > We think we know what's happening. This is something that is happening >> at >> > app upload time. Can you try setting a new version name for your app, >> then >> > passing the --no_batch option when using appcfg.sh? >> > >> > appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] >> >> >> Seems to solve it. I can't reproduce the error as I did by just >> modifying the spaces in comments in the css file anymore. >> >> Shawn >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To post to this group, send email to >> google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
Re: Carter Going a bit off topic, but in general I have always worked at places that stage deployments. That is - you have some environment only accessible by your team that reaches live data after your verification and QA more or less have determined that in the worse case scenario, your change is not destructive in a non-recoverable manner. Alternating versions is a very good way to do this; it also offers you a very easy rollback path. Being able to rollback quickly is absolutely key to working fast when things go sour. If it were me, I'd always alternate versions on deploy and manually switch versions when I have confidence the new version is good, but you've got to find that practice that works best for you. There are bugs that only rear their heads in production. The App Engine team more or less does major version releases by deploying to test clusters, internal clusters, and then, via canarying, to the production cluster. The way staging is usually done for new APIs is that new APIs are usually available in production before we announce the release (they may only be accessible to our whitelisted apps) so we can test that, in production (because production is always a jungle), the new APIs work well. We never do a rollout without first having a rollback plan, which is what you get by alternating versions when you deploy your applications. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Fri, Jan 13, 2012 at 12:40 PM, Carter Maslan wrote: > Ikai - > > Our site was unusable for 30 minutes while we quickly downloaded the > 1.6.1.1 fix and redeployed with the new SDK. > > We could have deployed in two phases with a different version so that we > could have discovered the bug prior to being live. > > Is it best practice to alternate between versions with *each and every* > deployment in order to catch deployment-specific bugs? > Or do you think your deployment-related testing is sufficiently good that > we can rely on the integrity of deployment? > > thanks, > Carter > > > > On Wed, Jan 11, 2012 at 5:22 PM, Ikai Lan (Google) wrote: > >> 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:38 PM, Shawn Brown >> wrote: >> >>> > We think we know what's happening. This is something that is happening >>> at >>> > app upload time. Can you try setting a new version name for your app, >>> then >>> > passing the --no_batch option when using appcfg.sh? >>> > >>> > appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] >>> >>> >>> Seems to solve it. I can't reproduce the error as I did by just >>> modifying the spaces in comments in the css file anymore. >>> >>> Shawn >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> To post to this group, send email to >>> google-appengine-java@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-appengine-java+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine-java?hl=en. >>> >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To post to this group, send email to >> google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Re: problem with Content-type: null with css files
thanks for the tips. We will start alternating versions with each deployment. I have another question about managing for queues that I will post under a distinct topic. thanks, Carter On Fri, Jan 13, 2012 at 3:16 PM, Ikai Lan (Google) wrote: > Re: Carter > > Going a bit off topic, but in general I have always worked at places that > stage deployments. That is - you have some environment only accessible by > your team that reaches live data after your verification and QA more or > less have determined that in the worse case scenario, your change is not > destructive in a non-recoverable manner. Alternating versions is a very > good way to do this; it also offers you a very easy rollback path. Being > able to rollback quickly is absolutely key to working fast when things go > sour. If it were me, I'd always alternate versions on deploy and manually > switch versions when I have confidence the new version is good, but you've > got to find that practice that works best for you. There are bugs that only > rear their heads in production. > > The App Engine team more or less does major version releases by deploying > to test clusters, internal clusters, and then, via canarying, to the > production cluster. The way staging is usually done for new APIs is that > new APIs are usually available in production before we announce the release > (they may only be accessible to our whitelisted apps) so we can test that, > in production (because production is always a jungle), the new APIs work > well. We never do a rollout without first having a rollback plan, which is > what you get by alternating versions when you deploy your applications. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > plus.ikailan.com | twitter.com/ikai > > > > On Fri, Jan 13, 2012 at 12:40 PM, Carter Maslan wrote: > >> Ikai - >> >> Our site was unusable for 30 minutes while we quickly downloaded the >> 1.6.1.1 fix and redeployed with the new SDK. >> >> We could have deployed in two phases with a different version so that we >> could have discovered the bug prior to being live. >> >> Is it best practice to alternate between versions with *each and every* >> deployment in order to catch deployment-specific bugs? >> Or do you think your deployment-related testing is sufficiently good that >> we can rely on the integrity of deployment? >> >> thanks, >> Carter >> >> >> >> On Wed, Jan 11, 2012 at 5:22 PM, Ikai Lan (Google) wrote: >> >>> 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:38 PM, Shawn Brown >> > wrote: >>> > We think we know what's happening. This is something that is happening at > app upload time. Can you try setting a new version name for your app, then > passing the --no_batch option when using appcfg.sh? > > appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] Seems to solve it. I can't reproduce the error as I did by just modifying the spaces in comments in the css file anymore. Shawn -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> To post to this group, send email to >>> google-appengine-java@googlegroups.com. >>> To unsubscribe from this group, send email to >>> google-appengine-java+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine-java?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine for Java" group. >> To post to this group, send email to >> google-appengine-java@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine-java+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine-java?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-
Re: [appengine-java] Re: problem with Content-type: null with css files
Just to be clear though, in this case, we *should* have been able to trust the tool (the SDK) to upload the file correctly. I mean there should be some sort of checks and balances for a system like that. In this case, I am deploying to my staging system, seeing the problems with CSS and then being like 'what the f*ck'? If I had had to get a patch out to production quickly, then this would have really screwed things up for me. Getting you guys (Google) to pay attention to this stuff took *weeks* and then another week+ to even get a resolution. I know everyone is working hard and everyone is doing a great job and I really appreciate that, but for people to have good opinions and a trusting sense of GAE, I think that bugs sent to the issue tracker should be at least responded to within 24-48 hours. Even if it is something as simple as "we are looking into it". I do that with my own open source projects and I'm just one guy. Google certainly has more resources than I do, so there should be no excuse for letting major bugs sit in the queue for that long. Having to call up Ikai and say hey dude, could you please look into this major deployment issue, just isn't sustainable. thanks for listening. jon On Fri, Jan 13, 2012 at 3:16 PM, Ikai Lan (Google) wrote: > Re: Carter > > Going a bit off topic, but in general I have always worked at places that > stage deployments. That is - you have some environment only accessible by > your team that reaches live data after your verification and QA more or > less have determined that in the worse case scenario, your change is not > destructive in a non-recoverable manner. Alternating versions is a very > good way to do this; it also offers you a very easy rollback path. Being > able to rollback quickly is absolutely key to working fast when things go > sour. If it were me, I'd always alternate versions on deploy and manually > switch versions when I have confidence the new version is good, but you've > got to find that practice that works best for you. There are bugs that only > rear their heads in production. > > The App Engine team more or less does major version releases by deploying > to test clusters, internal clusters, and then, via canarying, to the > production cluster. The way staging is usually done for new APIs is that > new APIs are usually available in production before we announce the release > (they may only be accessible to our whitelisted apps) so we can test that, > in production (because production is always a jungle), the new APIs work > well. We never do a rollout without first having a rollback plan, which is > what you get by alternating versions when you deploy your applications. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > plus.ikailan.com | twitter.com/ikai > > > > On Fri, Jan 13, 2012 at 12:40 PM, Carter Maslan wrote: > >> Ikai - >> >> Our site was unusable for 30 minutes while we quickly downloaded the >> 1.6.1.1 fix and redeployed with the new SDK. >> >> We could have deployed in two phases with a different version so that we >> could have discovered the bug prior to being live. >> >> Is it best practice to alternate between versions with *each and every* >> deployment in order to catch deployment-specific bugs? >> Or do you think your deployment-related testing is sufficiently good that >> we can rely on the integrity of deployment? >> >> thanks, >> Carter >> >> >> >> On Wed, Jan 11, 2012 at 5:22 PM, Ikai Lan (Google) wrote: >> >>> 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:38 PM, Shawn Brown >> > wrote: >>> > We think we know what's happening. This is something that is happening at > app upload time. Can you try setting a new version name for your app, then > passing the --no_batch option when using appcfg.sh? > > appcfg.sh --no_batch update [YOUR_WAR_DIRECTORY] Seems to solve it. I can't reproduce the error as I did by just modifying the spaces in comments in the css file anymore. Shawn -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google App Engine for Java" group. >>> To post to this group, send email to >>> google-appengine-java@googleg
Re: [appengine-java] Re: problem with Content-type: null with css files
One thing that would make this helpful would be the ability to automatically delete old versions. The current limit of 10 versions means I have to manually go through and delete old ones before I can deploy new ones. It would be nice to automate a "scrolling window" of versions. Of course, not all versions can be scrolled off; our "maintenance mode" version (never used, but there for emergencies) should always remain. appcfg.sh needs a way to list versions and delete individuals. Jeff On Sat, Jan 14, 2012 at 9:52 AM, andrew wrote: > A FYI about alternating versions for deployment to production... > > Our build script names the version according data from SVN (GIT would > be similar), as a working copy (name = data and time), revision > (name=r123), or tag (name = tag name = our release version number). > > Then the uploaded versions in appengine Dashboard all show either with > their release number (or revision, or date). > You can have up to 10 of them uploaded in production, working against > production data - but just one as the 'default'... > > On doing a new release/deploy to production (after previously testing > on another appid in integration and qa), we test the basics via the > specific version urlif everything looks fine we then make the new > version the default. > > If something goes wrong, you can quickly sqitch back to any of the > previous 9 releases you have made, usually the penultimate one off > course. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to google-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
