This is more related to IPv6. The new dev_appserver seems to like IPv6 too much and it is not related to Chrome. Just open http://[::1]:8080 instead or as you have already done explicitly start at your IPv4 localhost (127.0.0.1).
On Thursday, March 28, 2013 7:20:39 AM UTC+1, GAEfan wrote: > > Not sure if any of you have experienced this yet... > > Strange behavior with the new "Built-in Asynchronous DNS" in the new > Chrome release... (Using OSX 10.7.5, AppEngineLauncher 1.7.6.) > > I can no longer access "localhost". If I set the dev_appserver flag "--host > 127.0.0.1", it seems to fix the problem. > > If I disable the "Built-in Asynchronous DNS" flag in chrome:flags, it > works fine. > > Is this a Chrome bug, or AppEngine bug, where we have to explicitly link > localhost to 127.0.0.1 using the --host flag? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
