[google-appengine] Re: Mail Service Of Google App Engine (Standard) is very slow & delayed in sending mails.

['Denis T (Google Cloud Platform Support)' via Google App Engine]

Hello Mohammad,

The App Engine Mail API is indeed a deprecated service. The link 
 that you have 
mentioned also contains the following line:
*“This solution is no longer recommended: This page describes how to use a 
legacy App Engine service.”*

However, as I understand, your app is using the Mail API in Java 8 runtime 
and the issue you are experiencing is its latency (not that the service is 
not working in Java 8 runtime). 

Unfortunately, there is no other workaround that we can offer for a 
deprecated service besides using an alternative solution offered in this 
 
article of the GCP documentation.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2af0130b-7991-4911-863f-f79498ba6f6do%40googlegroups.com.

[google-appengine] Re: Communication between Java services given IP address

['George (Cloud Platform Support)' via Google App Engine]

Hello Luca, 

You may consider an address in the form of: 
https://VERSION_ID-dot-SERVICE_ID-dot-PROJECT_ID.REGION_ID.r.appspot.com
as detailed on the "Communicating Between Your Services" documentation page 
.
 
You may profit from reading Microservices Architecture on Google App Engine 

 
as well. 

This discussion group is oriented more towards general opinions, trends, 
and issues of general nature touching the app engine. For coding and 
program architecture, as well as organizing inter-service communication, 
you may be better served in dedicated forums such as stackoverflow, where 
experienced programmers are within reach and ready to help.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/abfb2721-17e3-44ed-8bcd-41ed455ea149o%40googlegroups.com.

[google-appengine] Communication between Java services given IP address

['Luca Lupo' via Google App Engine]

Hi There,

I have 2 services: service1 and service2 both deployed using docker on 
Google cloud. service1 contains a table where it maps all instances of 
service2 and when needed will send message (REST request) to a specific 
instance of service2. 

Everything works if I use the full URL address that Google cloud provide 
for the service but I want to send the message to a specific instance (by 
using the instance ip address). The use case is the following: I have one 
instance of service1 that sends messages to instances of service2 to tell 
which data to load. Each instance of service2 might need to load different 
data. All instances of service2 ping regularly service1 to communicate 
their own IP addresses and statuses, so that service1 knows which one is 
available and which not.

However, it doesn't look like the REST api gets hit on any instance of 
service2 when service1 uses service2 instance IP address.

Any hint on how to achieve this?

Thanks!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f1b4e961-3b1e-4dec-b1df-106942bf9b70o%40googlegroups.com.

[google-appengine] Re: How to enable Managed SSL on App Engine when using CloudFlare CDN

[Zorion Arrizabalaga]

Hi,

I'm not sure if this old post is of interest of anyone, but just in case I 
recently worked on it:
I don't know if cloudflare Full Strict is working with the cached version 
(proxy), but I got it work with the non-cached cloudflare dns. Since the 
request goes directly to AppEngine and CloudFlare only works as DNS server 
the let's encrypt certificate can be generated automatically in GAE.
I'm worried that you may need to disable the cache every 4 months in order 
to get the new certificate (and I'm not sure if it works, we will see it in 
4 months!)

As mentioned, if you re-enable the cache (proxy) when you have the let's 
encrypt certificate in you GAE, you will have again your CloudFlare SSL 
certificate for the proxy and it will talk to a valid Full Strict SSL 
certificate in GAE during 4 months.

Cheers!
Zorion

El viernes, 6 de octubre de 2017, 1:44:39 (UTC+2), Leonard Austin escribió:
>
> I'm also interested in this post. I'm not sure how creating a sub domain 
> of w3.example.com helps as will it not just create a managed certificate 
> from LetsEncrypt for w3 (not naked or www)? I think LetsEncrypt uses DNS 
> verification, which I assume is something GAE is handling behind the 
> scenes. If cloudflare is turned on and sits between LetsEncrypt 
> verification method and App Engine then I'm not sure GCP is able to create 
> a DNS record that LetsEncrypt can see? 
>
>
> On Tuesday, 3 October 2017 03:05:32 UTC+1, Kamran (Google Cloud Support) 
> wrote:
>>
>>
>> Managed security will need to check existence of canonical name (CNAME) 
>> record with the value of *ghs.googlehosted.com 
>> * for your domain/subdomain. If you're 
>> serving *www.example.com * on CloudFlare, you 
>> may map *w3.example.com * as custom sub-domain on 
>> GAE and enable managed security for it. Please try it and let me know how 
>> it works.
>>
>>
>>
>>
>> On Monday, October 2, 2017 at 11:49:20 AM UTC-4, Leigh McCulloch wrote:
>>>
>>> While that works it's not completely secure, only Full SSL (strict) or 
>>> Full SSL (origin ca)* is, not plain Full SSL. In Full SSL mode Cloudflare 
>>> doesn't verify the common name on the certificate served by AppEngine which 
>>> is why it works as you described. If I enable Full SSL (strict) using the 
>>> setup you described it fails because the certificate AppEngine is serving 
>>> is for example.appspot.com and not example.com.
>>>
>>> What I had hoped to do was enable managed security on AppEngine so that 
>>> AppEngine served a certificate with the correct common name. But it seems 
>>> like AppEngine does DNS checks before allowing the certificate to work.
>>>
>>> Is there anyway to make this work?
>>>
>>> Leigh
>>>
>>> * Note: Full SSL (origin ca) is also not supported by AppEngine, because 
>>> AppEngine doesn't allow the use of certificates that have been signed by a 
>>> CA that isn't a trusted CA.
>>>
>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5b7384d9-7d18-4742-a7a1-5b3b9684a0fdo%40googlegroups.com.