Re: [google-appengine] Serious bug in Push to Deploy

[Brad Abrams]

I am sorry you have hit this issue.Can I get your project ID so we can
investigate?

..brad


On Thu, Apr 10, 2014 at 9:52 PM, GAEfan  wrote:

> When deploying using Push to Deploy, all my static files are returning
> 404's.  Spent all day trying to find the issue, to no avail.
>
> If I deploy using appcfg or GAE Launcher, everything is fine.  I have seen
> others have had this same issue.
>
> So, there is a serious bug in Push to Deploy.
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

Thanks for all the information. I especially like the blog post by Jeff. I 
also found this on 
StackOverflow
 which 
seems useful.

Having said all that, I raised this question of naked domains again on 
StackOverflow 
and someone pointed 
outthat
 there is a new settings page at 
https://console.developers.google.com/project that allows you to link naked 
domains to App Engine! I am trying it out now and will report back. I bet 
it just redirects naked http domains like the original functionality though.

On Thursday, April 10, 2014 11:39:20 PM UTC+1, Jeff Schnitzer wrote:
>
> Unless CF provides some way of rewriting the Host: header, it won't 
> work because ultimately Google will reject the naked domain request. A 
> long time ago CF actually provided this ability, but then they removed 
> it for reasons I do not understand. You can always ask to bring it 
> back. 
>
> We use CF for SSL (see 
> http://blorn.com/post/20185054195/ssl-for-your-domain-on-google-app-engine),
>  
>
> but we wouldn't try this trick with naked domains even if it worked - 
> you'd be permanently dependent on CF. I like being able to yank them 
> out of the pipeline if necessary. 
>
> Jeff 
>
>
> On Thu, Apr 10, 2014 at 2:44 PM, PK > 
> wrote: 
> > I have read in this list that others have gotten this to work. However, 
> I 
> > have not pursued it because the state of the art of this integration 
> means 
> > that traffic from CloudFlare Data Center(s) to Google Data Center(s) 
> will be 
> > unencrypted and this does not pass my end to end security standards. 
> > 
> > PK 
> > http://www.gae123.com 
> > 
> > On April 10, 2014 at 12:31:53 PM, Dan (uvic...@gmail.com ) 
> wrote: 
> > 
> > Thanks for the info. Interesting that naked domains may work with 
> > CloudFlare's Flexible SSL option. 
> > 
> > Can anyone confirm this? I don't want to spend $20 for their pro plan 
> just 
> > to find out it does not work. CloudFlare's support has not been that 
> great. 
> > The support guy still thinks it should all just work even without SSL 
> turned 
> > on and advised me to 'check my settings on GAE'... 
> > 
> > On Thursday, April 10, 2014 7:30:53 PM UTC+1, barryhunter wrote: 
> >> 
> >> 
> >> 
> >>> 
> >>> I have set up the entry as so 'myapp.appspot.com CNAME mydomain.com' 
> but 
> >>> with no success. 
> >> 
> >> 
> >> That doesnt work on its own, because CloudFlare's proxy will send the 
> HTTP 
> >> Host header, still set to mydomain.com back to the origin (AppEngine) 
> - in 
> >> that situation, AppEngine has no way of knowing what appid, is meant to 
> >> serve the domain. 
> >> 
> >> 
> >> 
> >> 
> >>> 
> >>> 
> >>> If you have made naked domains work with GAE, how did you do it? 
> >> 
> >> 
> >> You need a proxy, capable of rewriting the http host header. There are 
> >> commerical services that offer this. 
> >> 
> >> I've done it previously using Varnish on a small VPS. quite easy to 
> setup 
> >> if have some basic linux knowledge. 
> >> 
> >> 
> >> And I do know edgecast CDN does offer http header rewriting, but not 
> tried 
> >> it with AppEngine. 
> >> 
> >> 
> >> People using CloudFlare with AppEngine, I think is using the SSL 
> option, 
> >> where the Flexible SSL option may well offer host header rewriting 
> (because 
> >> it reterminates SSL) - so using the SSL option, even if you dont 
> strictly 
> >> need SSL, might work. 
> >> 
> >> 
> > -- 
> > 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 google-appengi...@googlegroups.com . 
> > To post to this group, send email to 
> > google-a...@googlegroups.com. 
>
> > Visit this group at http://groups.google.com/group/google-appengine. 
> > For more options, visit https://groups.google.com/d/optout. 
> > 
> > -- 
> > 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 google-appengi...@googlegroups.com . 
> > To post to this group, send email to 
> > google-a...@googlegroups.com. 
>
> > Visit this group at http://groups.google.com/group/google-appengine. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send emai

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

The new Custom Domains settings page in Google Console does just map 
redirect naked domains to subdomains as with previous functionality. :-(

On Friday, April 11, 2014 10:59:24 AM UTC+1, Dan wrote:
>
> Thanks for all the information. I especially like the blog post by Jeff. I 
> also found this on 
> StackOverflow
>  which 
> seems useful.
>
> Having said all that, I raised this question of naked domains again on 
> StackOverflow 
> and someone pointed 
> outthat
>  there is a new settings page at 
> https://console.developers.google.com/project that allows you to link 
> naked domains to App Engine! I am trying it out now and will report back. I 
> bet it just redirects naked http domains like the original functionality 
> though.
>
> On Thursday, April 10, 2014 11:39:20 PM UTC+1, Jeff Schnitzer wrote:
>>
>> Unless CF provides some way of rewriting the Host: header, it won't 
>> work because ultimately Google will reject the naked domain request. A 
>> long time ago CF actually provided this ability, but then they removed 
>> it for reasons I do not understand. You can always ask to bring it 
>> back. 
>>
>> We use CF for SSL (see 
>> http://blorn.com/post/20185054195/ssl-for-your-domain-on-google-app-engine),
>>  
>>
>> but we wouldn't try this trick with naked domains even if it worked - 
>> you'd be permanently dependent on CF. I like being able to yank them 
>> out of the pipeline if necessary. 
>>
>> Jeff 
>>
>>
>> On Thu, Apr 10, 2014 at 2:44 PM, PK  wrote: 
>> > I have read in this list that others have gotten this to work. However, 
>> I 
>> > have not pursued it because the state of the art of this integration 
>> means 
>> > that traffic from CloudFlare Data Center(s) to Google Data Center(s) 
>> will be 
>> > unencrypted and this does not pass my end to end security standards. 
>> > 
>> > PK 
>> > http://www.gae123.com 
>> > 
>> > On April 10, 2014 at 12:31:53 PM, Dan (uvic...@gmail.com) wrote: 
>> > 
>> > Thanks for the info. Interesting that naked domains may work with 
>> > CloudFlare's Flexible SSL option. 
>> > 
>> > Can anyone confirm this? I don't want to spend $20 for their pro plan 
>> just 
>> > to find out it does not work. CloudFlare's support has not been that 
>> great. 
>> > The support guy still thinks it should all just work even without SSL 
>> turned 
>> > on and advised me to 'check my settings on GAE'... 
>> > 
>> > On Thursday, April 10, 2014 7:30:53 PM UTC+1, barryhunter wrote: 
>> >> 
>> >> 
>> >> 
>> >>> 
>> >>> I have set up the entry as so 'myapp.appspot.com CNAME mydomain.com' 
>> but 
>> >>> with no success. 
>> >> 
>> >> 
>> >> That doesnt work on its own, because CloudFlare's proxy will send the 
>> HTTP 
>> >> Host header, still set to mydomain.com back to the origin (AppEngine) 
>> - in 
>> >> that situation, AppEngine has no way of knowing what appid, is meant 
>> to 
>> >> serve the domain. 
>> >> 
>> >> 
>> >> 
>> >> 
>> >>> 
>> >>> 
>> >>> If you have made naked domains work with GAE, how did you do it? 
>> >> 
>> >> 
>> >> You need a proxy, capable of rewriting the http host header. There are 
>> >> commerical services that offer this. 
>> >> 
>> >> I've done it previously using Varnish on a small VPS. quite easy to 
>> setup 
>> >> if have some basic linux knowledge. 
>> >> 
>> >> 
>> >> And I do know edgecast CDN does offer http header rewriting, but not 
>> tried 
>> >> it with AppEngine. 
>> >> 
>> >> 
>> >> People using CloudFlare with AppEngine, I think is using the SSL 
>> option, 
>> >> where the Flexible SSL option may well offer host header rewriting 
>> (because 
>> >> it reterminates SSL) - so using the SSL option, even if you dont 
>> strictly 
>> >> need SSL, might work. 
>> >> 
>> >> 
>> > -- 
>> > 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 google-appengi...@googlegroups.com. 
>> > To post to this group, send email to google-a...@googlegroups.com. 
>> > Visit this group at http://groups.google.com/group/google-appengine. 
>> > For more options, visit https://groups.google.com/d/optout. 
>> > 
>> > -- 
>> > 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 google-appengi...@googlegroups.com. 
>> > To post to this group, send email to google-a...@googlegroups.com. 
>> > Visit this group at http://groups.google.com/group/google-appengine. 
>> > For mor

[google-appengine] Heartbleed Bug

[Vizay Soni]

Hi,

Does Google App Engine servers Vulnerable to
heartbleedBug?

*--vs*

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Updates happening very fast

[Ray]

A single entity update transaction (BeginTransaction>Get>Put>Commit) still 
takes around 150-200ms for me. Doesnt seems to be fast.


On Friday, April 11, 2014 12:45:59 AM UTC+8, PK wrote:
>
> Since around 1.9.2 rolled out I noticed that the updates in our 
> application are noticeably fast. Each update usually affects a few 
> datastore entities, and creates one, and is done within a transaction to 
> make sure that all these changes happen atomically.
>
> Has anybody else noticed anything similar? Anybody from Google who want to 
> claim credit for it? :-) I am asking because if I am the only one noticing 
> this we might have accidentally changed something on our end (e.g. somebody 
> turned off transactions…) and need to drop everything else and go 
> investigate.
>
> Thanks,
> PK
> http://www.gae123.com
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Updates happening very fast

[Ray]

You may really want to check your code. The commit phase alone takes around 
150ms. You sure you are using HRD and transaction?

On Friday, April 11, 2014 12:45:59 AM UTC+8, PK wrote:
>
> Since around 1.9.2 rolled out I noticed that the updates in our 
> application are noticeably fast. Each update usually affects a few 
> datastore entities, and creates one, and is done within a transaction to 
> make sure that all these changes happen atomically.
>
> Has anybody else noticed anything similar? Anybody from Google who want to 
> claim credit for it? :-) I am asking because if I am the only one noticing 
> this we might have accidentally changed something on our end (e.g. somebody 
> turned off transactions…) and need to drop everything else and go 
> investigate.
>
> Thanks,
> PK
> http://www.gae123.com
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Heartbleed Bug

[Charlie Fineman]

Please see the following:
http://googleonlinesecurity.blogspot.com/2014/04/google-services-updated-to-address.html

AppEngine front ends have had the appropriate patches applied.


On Fri, Apr 11, 2014 at 4:19 AM, Vizay Soni  wrote:

> Hi,
>
> Does Google App Engine servers Vulnerable to 
> heartbleedBug?
>
> *--vs*
>
> --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Serious bug in Push to Deploy

[GAEfan]

Hi Brad:

Thank you for responding.

I may have narrowed it down a bit...  It seems to only happen on our apps 
running Django (Django non-rel, with our own Django pkg). 

When using Flask, or no package, it works fine.  Although, I have not 
tested the remote_api others have complained about.

I have seen others have this issue running various packages.  Here are a 
couple:

https://groups.google.com/forum/#!topic/google-appengine/t7L4URlUr0A
http://stackoverflow.com/questions/20181900/gae-php-runs-localhost-but-results-in-404-in-all-files-after-pushed-using-push

Again, when I use push-to-deploy, the static files are all 404'd, even 
though the paths are correct.  When I deploy using the 
GoogleAppEngineLauncher, it works fine.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[husayt]

This new google cloud DNS , might be interesting:
https://developers.google.com/cloud-dns/

but I have not looked into it.

On Friday, 11 April 2014 11:21:22 UTC+1, Dan wrote:
>
> The new Custom Domains settings page in Google Console does just map 
> redirect naked domains to subdomains as with previous functionality. :-(
>
> On Friday, April 11, 2014 10:59:24 AM UTC+1, Dan wrote:
>>
>> Thanks for all the information. I especially like the blog post by Jeff. 
>> I also found this on 
>> StackOverflow
>>  which 
>> seems useful.
>>
>> Having said all that, I raised this question of naked domains again on 
>> StackOverflow 
>> and someone pointed 
>> outthat
>>  there is a new settings page at 
>> https://console.developers.google.com/project that allows you to link 
>> naked domains to App Engine! I am trying it out now and will report back. I 
>> bet it just redirects naked http domains like the original functionality 
>> though.
>>
>> On Thursday, April 10, 2014 11:39:20 PM UTC+1, Jeff Schnitzer wrote:
>>>
>>> Unless CF provides some way of rewriting the Host: header, it won't 
>>> work because ultimately Google will reject the naked domain request. A 
>>> long time ago CF actually provided this ability, but then they removed 
>>> it for reasons I do not understand. You can always ask to bring it 
>>> back. 
>>>
>>> We use CF for SSL (see 
>>>
>>> http://blorn.com/post/20185054195/ssl-for-your-domain-on-google-app-engine),
>>>  
>>>
>>> but we wouldn't try this trick with naked domains even if it worked - 
>>> you'd be permanently dependent on CF. I like being able to yank them 
>>> out of the pipeline if necessary. 
>>>
>>> Jeff 
>>>
>>>
>>> On Thu, Apr 10, 2014 at 2:44 PM, PK  wrote: 
>>> > I have read in this list that others have gotten this to work. 
>>> However, I 
>>> > have not pursued it because the state of the art of this integration 
>>> means 
>>> > that traffic from CloudFlare Data Center(s) to Google Data Center(s) 
>>> will be 
>>> > unencrypted and this does not pass my end to end security standards. 
>>> > 
>>> > PK 
>>> > http://www.gae123.com 
>>> > 
>>> > On April 10, 2014 at 12:31:53 PM, Dan (uvic...@gmail.com) wrote: 
>>> > 
>>> > Thanks for the info. Interesting that naked domains may work with 
>>> > CloudFlare's Flexible SSL option. 
>>> > 
>>> > Can anyone confirm this? I don't want to spend $20 for their pro plan 
>>> just 
>>> > to find out it does not work. CloudFlare's support has not been that 
>>> great. 
>>> > The support guy still thinks it should all just work even without SSL 
>>> turned 
>>> > on and advised me to 'check my settings on GAE'... 
>>> > 
>>> > On Thursday, April 10, 2014 7:30:53 PM UTC+1, barryhunter wrote: 
>>> >> 
>>> >> 
>>> >> 
>>> >>> 
>>> >>> I have set up the entry as so 'myapp.appspot.com CNAME mydomain.com' 
>>> but 
>>> >>> with no success. 
>>> >> 
>>> >> 
>>> >> That doesnt work on its own, because CloudFlare's proxy will send the 
>>> HTTP 
>>> >> Host header, still set to mydomain.com back to the origin 
>>> (AppEngine) - in 
>>> >> that situation, AppEngine has no way of knowing what appid, is meant 
>>> to 
>>> >> serve the domain. 
>>> >> 
>>> >> 
>>> >> 
>>> >> 
>>> >>> 
>>> >>> 
>>> >>> If you have made naked domains work with GAE, how did you do it? 
>>> >> 
>>> >> 
>>> >> You need a proxy, capable of rewriting the http host header. There 
>>> are 
>>> >> commerical services that offer this. 
>>> >> 
>>> >> I've done it previously using Varnish on a small VPS. quite easy to 
>>> setup 
>>> >> if have some basic linux knowledge. 
>>> >> 
>>> >> 
>>> >> And I do know edgecast CDN does offer http header rewriting, but not 
>>> tried 
>>> >> it with AppEngine. 
>>> >> 
>>> >> 
>>> >> People using CloudFlare with AppEngine, I think is using the SSL 
>>> option, 
>>> >> where the Flexible SSL option may well offer host header rewriting 
>>> (because 
>>> >> it reterminates SSL) - so using the SSL option, even if you dont 
>>> strictly 
>>> >> need SSL, might work. 
>>> >> 
>>> >> 
>>> > -- 
>>> > 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 google-appengi...@googlegroups.com. 
>>> > To post to this group, send email to google-a...@googlegroups.com. 
>>> > Visit this group at http://groups.google.com/group/google-appengine. 
>>> > For more options, visit https://groups.google.com/d/optout. 
>>> > 
>>> > -- 
>>> > You received this message because you are subscribed to the Google 
>>> Groups 
>>> > "Goog

Re: [google-appengine] App Engine and naked/apex domains

[Barry Hunter]

On 11 April 2014 16:36, husayt  wrote:

> This new google cloud DNS , might be interesting:
> https://developers.google.com/cloud-dns/
> but I have not looked into it.
>

It doesnt help directly. It doesnt support ALIAS records nor particular
intergration with AppEngine.


... it it offers no additional features beyond what would get at any other
DNS provider. Its just useful if want to handle everything via Google.


The new domain mapping feature just found, does indeed look like it will
sort it :) Could use it with couldflare, with cloud-dns, or what ever dns
provider you want.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

I raised this issue because I saw Google released their Cloud DNS service 
and CloudFlare released there CNAME flattening service.

I was also VERY hopeful about the new Google Console App Engine domain 
mapping feature. Unfortunately, for me, it just redirects naked domains to 
subdomains which is not what I want.

Also CloudFlare just confirmed that the Flexible SSL option on their Pro 
Plan will also not work with GAE naked domains.

I guess I am stuck as I really don't want to run a reverse proxy on a VPS 
somewhere.

On Friday, April 11, 2014 4:40:46 PM UTC+1, barryhunter wrote:
>
>
>
>
> On 11 April 2014 16:36, husayt > wrote:
>
>> This new google cloud DNS , might be interesting:
>> https://developers.google.com/cloud-dns/
>> but I have not looked into it.
>>
>
> It doesnt help directly. It doesnt support ALIAS records nor particular 
> intergration with AppEngine. 
>
>
> ... it it offers no additional features beyond what would get at any other 
> DNS provider. Its just useful if want to handle everything via Google. 
>
>
> The new domain mapping feature just found, does indeed look like it will 
> sort it :) Could use it with couldflare, with cloud-dns, or what ever dns 
> provider you want. 
>  
>  

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Barry Hunter]

On 11 April 2014 16:56, Dan  wrote:

> I raised this issue because I saw Google released their Cloud DNS service
> and CloudFlare released there CNAME flattening service.
>
> I was also VERY hopeful about the new Google Console App Engine domain
> mapping feature. Unfortunately, for me, it just redirects naked domains to
> subdomains which is not what I want.
>

Are you sure about that?

When I looked at the control panel, you can set a mapping from the naken
domain to Appengine.

For a redirect to work, it would have to tell you to setup the DNS for the
naked domain, AND the DNS for whatever subdomain it redirects to.



In fact I just tried it, with a spare domain I had already verified with
Google. I added it in the cloud control panel, then did a request

# GET http://216.239.32.21/ -HHost:geograph.co.uk -usedS

... I get the content from a AppEngine App (geodatastore).

No Redirect, no where else have setup a mapping from this domain to
appengine. Note however also this mapping doesnt exist in DNS either (I'm
just using it for testing purposes. . )


Maybe you are getting the redirect, because you have previouslly set it up
in the Google Apps control panel? So its still managing the redirect, if so
need to delete that so that the new cloud control panel can configure what
happens with the domain.





>
> Also CloudFlare just confirmed that the Flexible SSL option on their Pro
> Plan will also not work with GAE naked domains.
>
> I guess I am stuck as I really don't want to run a reverse proxy on a VPS
> somewhere.
>
> On Friday, April 11, 2014 4:40:46 PM UTC+1, barryhunter wrote:
>
>>
>>
>>
>> On 11 April 2014 16:36, husayt  wrote:
>>
>>> This new google cloud DNS , might be interesting:
>>> https://developers.google.com/cloud-dns/
>>> but I have not looked into it.
>>>
>>
>> It doesnt help directly. It doesnt support ALIAS records nor particular
>> intergration with AppEngine.
>>
>>
>> ... it it offers no additional features beyond what would get at any
>> other DNS provider. Its just useful if want to handle everything via
>> Google.
>>
>>
>> The new domain mapping feature just found, does indeed look like it will
>> sort it :) Could use it with couldflare, with cloud-dns, or what ever dns
>> provider you want.
>>
>>
>  --
> 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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Java ImageService and OrientationCorrection

[PK]

Could it be related to this issue:

https://code.google.com/p/googleappengine/issues/detail?id=8304


PK
http://www.gae123.com

On April 10, 2014 at 7:20:40 AM, Alejandro Gonzalez 
(alejandro.gonza...@nextinit.com) wrote:


Hello,

Im making some tests with the ImageService (in java) and the EXIF info for 
images. My problem is that when i use the ImageService to transform images 
(crop+resize) the EXIF info for the image is used, and therefor the image gets 
rotated acording to his EXIF information.

Im uploading the image from an iPad, and i cant figure out how to ignore this 
EXIF rotation info when using the ImageService.applyTransform

I could't find any documentation but the javadoc of the OrientationCorrection 
in 
https://developers.google.com/appengine/docs/java/javadoc/com/google/appengine/api/images/InputSettings.OrientationCorrection

However, this is not solving my problem as seems to do nothing and the image 
keeps rotating when i try to resize it. This is the code:



                CompositeTransform cp = 
ImagesServiceFactory.makeCompositeTransform();
                cp.concatenate(ImagesServiceFactory.makeCrop(p_leftX, p_topY, 
p_rightX, p_bottomY));
                cp.concatenate(ImagesServiceFactory.makeResize(500, 500));
                
                InputSettings is = new InputSettings();
                
is.setOrientationCorrection(InputSettings.OrientationCorrection.UNCHANGED_ORIENTATION);
                
                OutputSettings os = new 
OutputSettings(ImagesService.OutputEncoding.PNG);
                
                LOGGER.info("TRANSFORM IMAGE IGNORING EXIF");
                
                image = imagesService.applyTransform(cp, image, is, os);

Does anyone has a clue about how to ignore the EXIF info for an image when 
transforming it with the imageService? Does anyone know if the 
OrientationCorrection flag is working properly?

This is documented for phyton 
(https://developers.google.com/appengine/docs/python/images/functions) , but 
not for java (just JavaDoc)

Thanks in advance!
--
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Subdomain for GAE and GMail

[patrick conant]

Thanks, Vinny and Barry.  I followed the pointer to DNSimple, and confirmed
that they'll be able to meet my needs with a DNS Alias. Perfect!  I
appreciate the help.

-Pat.



On Thu, Apr 10, 2014 at 4:49 AM, Barry Hunter wrote:

>
>
>
> On 10 April 2014 10:19, Vinny P  wrote:
>
>> On Mon, Apr 7, 2014 at 10:44 PM, pdconant 
>>  wrote:
>>
>> Is it possible to use the same subdomain for both a Google App Engine app
>>> and for GMail?  For instance, imagine I wanted to have
>>> http://myapp.mycompany.com served by GAE and also use email address
>>> m...@myapp.mycompany.com.  For the GAE app, I'd need a CNAME pointing
>>> myapp.mycompany.com to "ghs.googlehosted.com."; and for GMail to work,
>>> I'd need MX records for "myapp.mycompany.com".  But I don't believe I
>>> can have CNAME and MX records for the same subdomain. I'm no DNS expert --
>>> I hope I'm missing something obvious to those more knowledgeable than
>>> myself.  Any ideas?
>>>
>>
>>
>>
>>  As you noted, it's difficult to have both a CNAME and MX records for the
>> same subdomain. Here's a detailed explanation of the issue:
>> http://serverfault.com/questions/18000/dns-subdomains-that-require-both-an-mx-record-and-a-cname
>>
>>
>> Unfortunately there's no way to avoid this problem,
>>
>>
> Or can just find a DNS provider that supports ALIAS records (sort of fake
> CNAMES, where the nameserver does the resolution, rather than a just
> returning a pointer)
>
>
> http://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root
>
> http://support.dnsimple.com/articles/differences-between-a-cname-alias-url/
>
>
> http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/CreatingAliasRRSets.html
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/IqRgUWK8Ouo/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

Amazing! It works! You can now serve naked domains with App Engine! 

Barry, you are correct I did have my naked domain mapped to www in Google 
Apps. However I removed the mapping prior to trying the new Google Console 
Custom Domain Settings. I just assumed Google did something stupid like by 
default redirect naked domains to www.

In the end what I needed to do was completely disassociate my App Engine 
app and my Google Apps account. Once I did this it all started to work. 
Hooray, this is a feature we have all been waiting for since 2009! Thanks 
Google I really appreciate the return of naked domain serving.

On Friday, April 11, 2014 5:16:36 PM UTC+1, barryhunter wrote:
>
>
>
>
> On 11 April 2014 16:56, Dan > wrote:
>
>> I raised this issue because I saw Google released their Cloud DNS service 
>> and CloudFlare released there CNAME flattening service.
>>
>> I was also VERY hopeful about the new Google Console App Engine domain 
>> mapping feature. Unfortunately, for me, it just redirects naked domains to 
>> subdomains which is not what I want.
>>
>
> Are you sure about that?
>
> When I looked at the control panel, you can set a mapping from the naken 
> domain to Appengine. 
>
> For a redirect to work, it would have to tell you to setup the DNS for the 
> naked domain, AND the DNS for whatever subdomain it redirects to. 
>
>
>
> In fact I just tried it, with a spare domain I had already verified with 
> Google. I added it in the cloud control panel, then did a request
>
> # GET http://216.239.32.21/ -HHost:geograph.co.uk -usedS
>
> ... I get the content from a AppEngine App (geodatastore). 
>
> No Redirect, no where else have setup a mapping from this domain to 
> appengine. Note however also this mapping doesnt exist in DNS either (I'm 
> just using it for testing purposes. . )
>
>
> Maybe you are getting the redirect, because you have previouslly set it up 
> in the Google Apps control panel? So its still managing the redirect, if so 
> need to delete that so that the new cloud control panel can configure what 
> happens with the domain. 
>
>
>
>  
>
>>  
>> Also CloudFlare just confirmed that the Flexible SSL option on their Pro 
>> Plan will also not work with GAE naked domains.
>>
>> I guess I am stuck as I really don't want to run a reverse proxy on a VPS 
>> somewhere.
>>
>> On Friday, April 11, 2014 4:40:46 PM UTC+1, barryhunter wrote:
>>
>>>
>>>
>>>
>>> On 11 April 2014 16:36, husayt  wrote:
>>>
 This new google cloud DNS , might be interesting:
 https://developers.google.com/cloud-dns/
 but I have not looked into it.

>>>
>>> It doesnt help directly. It doesnt support ALIAS records nor particular 
>>> intergration with AppEngine. 
>>>
>>>
>>> ... it it offers no additional features beyond what would get at any 
>>> other DNS provider. Its just useful if want to handle everything via 
>>> Google. 
>>>
>>>
>>> The new domain mapping feature just found, does indeed look like it will 
>>> sort it :) Could use it with couldflare, with cloud-dns, or what ever dns 
>>> provider you want. 
>>>  
>>>  
>>  -- 
>> 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 google-appengi...@googlegroups.com .
>> To post to this group, send email to 
>> google-a...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[Dan]

I should add that I guess this also means you don't need a Google Apps 
account for custom domains anymore! Another thing we have all been waiting 
for.

On Friday, April 11, 2014 8:54:24 PM UTC+1, Dan wrote:
>
> Amazing! It works! You can now serve naked domains with App Engine! 
>
> Barry, you are correct I did have my naked domain mapped to www in Google 
> Apps. However I removed the mapping prior to trying the new Google Console 
> Custom Domain Settings. I just assumed Google did something stupid like by 
> default redirect naked domains to www.
>
> In the end what I needed to do was completely disassociate my App Engine 
> app and my Google Apps account. Once I did this it all started to work. 
> Hooray, this is a feature we have all been waiting for since 2009! Thanks 
> Google I really appreciate the return of naked domain serving.
>
> On Friday, April 11, 2014 5:16:36 PM UTC+1, barryhunter wrote:
>>
>>
>>
>>
>> On 11 April 2014 16:56, Dan  wrote:
>>
>>> I raised this issue because I saw Google released their Cloud DNS 
>>> service and CloudFlare released there CNAME flattening service.
>>>
>>> I was also VERY hopeful about the new Google Console App Engine domain 
>>> mapping feature. Unfortunately, for me, it just redirects naked domains to 
>>> subdomains which is not what I want.
>>>
>>
>> Are you sure about that?
>>
>> When I looked at the control panel, you can set a mapping from the naken 
>> domain to Appengine. 
>>
>> For a redirect to work, it would have to tell you to setup the DNS for 
>> the naked domain, AND the DNS for whatever subdomain it redirects to. 
>>
>>
>>
>> In fact I just tried it, with a spare domain I had already verified with 
>> Google. I added it in the cloud control panel, then did a request
>>
>> # GET http://216.239.32.21/ -HHost:geograph.co.uk -usedS
>>
>> ... I get the content from a AppEngine App (geodatastore). 
>>
>> No Redirect, no where else have setup a mapping from this domain to 
>> appengine. Note however also this mapping doesnt exist in DNS either (I'm 
>> just using it for testing purposes. . )
>>
>>
>> Maybe you are getting the redirect, because you have previouslly set it 
>> up in the Google Apps control panel? So its still managing the redirect, if 
>> so need to delete that so that the new cloud control panel can configure 
>> what happens with the domain. 
>>
>>
>>
>>  
>>
>>>  
>>> Also CloudFlare just confirmed that the Flexible SSL option on their Pro 
>>> Plan will also not work with GAE naked domains.
>>>
>>> I guess I am stuck as I really don't want to run a reverse proxy on a 
>>> VPS somewhere.
>>>
>>> On Friday, April 11, 2014 4:40:46 PM UTC+1, barryhunter wrote:
>>>



 On 11 April 2014 16:36, husayt  wrote:

> This new google cloud DNS , might be interesting:
> https://developers.google.com/cloud-dns/
> but I have not looked into it.
>

 It doesnt help directly. It doesnt support ALIAS records nor particular 
 intergration with AppEngine. 


 ... it it offers no additional features beyond what would get at any 
 other DNS provider. Its just useful if want to handle everything via 
 Google. 


 The new domain mapping feature just found, does indeed look like it 
 will sort it :) Could use it with couldflare, with cloud-dns, or what ever 
 dns provider you want. 
  
  
>>>  -- 
>>> 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 google-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/google-appengine.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Heartbleed: do we need to renew the SSL certificates for appengine apps?

[Luca de Alfaro]

I am running an app on appengine that is secured by SSL certificates.  The 
certs are ONLY used on appengine.
Do I need to renew the certificates, after heartbleed? 
Could the private / signing keys of those certificates have been 
compromised? 

Luca

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

[Andrew Jessup]

Hi Everyone,

I'm happy to report that we have just added support for mapping custom 
domains to an App Engine application directly from within the Google 
Developers Console (https://console.developers.google.com/). This means 
that you can associate your domains without being required to purchase 
Google Apps for each domain first.

This isn't dependent on our recently released Cloud DNS service - although 
if you *are* looking for a great DNS, they do go well together :)

There are still some features we're looking to add to this - notably, 
support for SSL for custom domains (which is still available if you use 
Google Apps to associate a domain, and is available automattically from 
your *.appspot.com URLs). In the meantime, we hope you find this to be a 
more effective and simpler way to set up your App Engine apps.

Since Google Apps is no longer necessary, from today we are no longer 
offering the Jump Start credit to new applicants. Those who have already 
been awarded the credit will still be able to draw down from any unused 
credit on their account, and if you have recently applied prior to today 
then we will still review your application. However new applications will 
not be accepted.

Thanks for your patience.

Regards,

Andrew
Product Manager, Google Cloud Platform

On Thursday, 27 March 2014 20:39:24 UTC+1, Vinny P wrote:
>
> On Thu, Mar 27, 2014 at 2:26 PM, Barry Hunter 
> 
> > wrote:
>
>> Can't just use cloud-dns to CNAME your domain to ghs.googlehosted.com - 
>> *without *using Google Apps, because still needs to know the 
>> domain-to-appid mapping. 
>>
>> So can use Cloud-DNS, but still need Google Apps *too*. 
>>
>
>
> I agree with Barry. I read through the Cloud DNS documentation, but unless 
> I missed something, I don't see a way to associate domains with specific 
> applications. 
>
> For instance, I can create a managed zone and associate it with a project 
> by calling this REST command: 
> https://developers.google.com/cloud-dns/api/v1beta1/managedZones/create . 
> But where is the association between domain/project to App Engine ID?
>   
>  
> -
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> App Engine Code Samples: http://www.learntogoogleit.com
>   
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

[GAEfan]

Thank you for the update, Andrew.  Something that has been needed for quite 
some time.

Can you walk me through setting it up so we can set our MX records to use 
gmail as our email service, without using Google Apps?  Previously, we set 
the MX records to aspmx.l.google.com or aspmx2.googlemail.com.  Without 
Google Apps, those mappings will get lost?  Of course, we can use the gmail 
independently, but it would be nice to be able to have catch-all forwarding.

Thanks again.

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine VM-based Backends - Trusted Tester Sign-up

[Chris Ramsdale]

yes, you can use JDO, JPA, Objectify, etc. when running on a Managed VM
(previously referred to as "VM Backend").  let me know if you need more
clarification.

-- Chris

On Wednesday, April 9, 2014, Rafael  wrote:

> Also in my case. The only reason why we stick with appengine and are not
> on GCE is because of the datastore lock-in.
>
> Java being Java, I don't know how difficult it would be to abstract the
> JSON api into the JDO and Datastore java interfaces?
>
>
> On Wed, Apr 9, 2014 at 12:48 AM, Trung Pham 
> 
> > wrote:
>
>> Do you know if I can access Google datastore using the appengine SDK
>> rather than the JSON api from the VM backend? This will certainly make
>> things much easier for me.
>>
>> Appengine SDK
>> https://developers.google.com/appengine/docs/go/datastore/reference
>>
>> --
>> 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 
>> google-appengine+unsubscr...@googlegroups.com
>> .
>> To post to this group, send email to 
>> google-appengine@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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 
> google-appengine+unsubscr...@googlegroups.com
> .
> To post to this group, send email to 
> google-appengine@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] App Engine and naked/apex domains

[husayt]

Dan, I am glad to hear you managed to get this working.

Did you do it through google console or some other place? It will very 
useful if you could share what steps we need to take for this.

Thanks.

On Friday, 11 April 2014 21:08:17 UTC+1, Dan wrote:
>
> I should add that I guess this also means you don't need a Google Apps 
> account for custom domains anymore! Another thing we have all been waiting 
> for.
>
> On Friday, April 11, 2014 8:54:24 PM UTC+1, Dan wrote:
>>
>> Amazing! It works! You can now serve naked domains with App Engine! 
>>
>> Barry, you are correct I did have my naked domain mapped to www in Google 
>> Apps. However I removed the mapping prior to trying the new Google Console 
>> Custom Domain Settings. I just assumed Google did something stupid like by 
>> default redirect naked domains to www.
>>
>> In the end what I needed to do was completely disassociate my App Engine 
>> app and my Google Apps account. Once I did this it all started to work. 
>> Hooray, this is a feature we have all been waiting for since 2009! Thanks 
>> Google I really appreciate the return of naked domain serving.
>>
>> On Friday, April 11, 2014 5:16:36 PM UTC+1, barryhunter wrote:
>>>
>>>
>>>
>>>
>>> On 11 April 2014 16:56, Dan  wrote:
>>>
 I raised this issue because I saw Google released their Cloud DNS 
 service and CloudFlare released there CNAME flattening service.

 I was also VERY hopeful about the new Google Console App Engine domain 
 mapping feature. Unfortunately, for me, it just redirects naked domains to 
 subdomains which is not what I want.

>>>
>>> Are you sure about that?
>>>
>>> When I looked at the control panel, you can set a mapping from the naken 
>>> domain to Appengine. 
>>>
>>> For a redirect to work, it would have to tell you to setup the DNS for 
>>> the naked domain, AND the DNS for whatever subdomain it redirects to. 
>>>
>>>
>>>
>>> In fact I just tried it, with a spare domain I had already verified with 
>>> Google. I added it in the cloud control panel, then did a request
>>>
>>> # GET http://216.239.32.21/ -HHost:geograph.co.uk -usedS
>>>
>>> ... I get the content from a AppEngine App (geodatastore). 
>>>
>>> No Redirect, no where else have setup a mapping from this domain to 
>>> appengine. Note however also this mapping doesnt exist in DNS either (I'm 
>>> just using it for testing purposes. . )
>>>
>>>
>>> Maybe you are getting the redirect, because you have previouslly set it 
>>> up in the Google Apps control panel? So its still managing the redirect, if 
>>> so need to delete that so that the new cloud control panel can configure 
>>> what happens with the domain. 
>>>
>>>
>>>
>>>  
>>>
  
 Also CloudFlare just confirmed that the Flexible SSL option on their 
 Pro Plan will also not work with GAE naked domains.

 I guess I am stuck as I really don't want to run a reverse proxy on a 
 VPS somewhere.

 On Friday, April 11, 2014 4:40:46 PM UTC+1, barryhunter wrote:

>
>
>
> On 11 April 2014 16:36, husayt  wrote:
>
>> This new google cloud DNS , might be interesting:
>> https://developers.google.com/cloud-dns/
>> but I have not looked into it.
>>
>
> It doesnt help directly. It doesnt support ALIAS records nor 
> particular intergration with AppEngine. 
>
>
> ... it it offers no additional features beyond what would get at any 
> other DNS provider. Its just useful if want to handle everything via 
> Google. 
>
>
> The new domain mapping feature just found, does indeed look like it 
> will sort it :) Could use it with couldflare, with cloud-dns, or what 
> ever 
> dns provider you want. 
>  
>  
  -- 
 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 google-appengi...@googlegroups.com.
 To post to this group, send email to google-a...@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-appengine.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.