I have no idea where to report this, so I'm posting it here.
http://loggedoutsession.appspot.com/
That URL is being used to phish for twitter login details. Please shut it
down, thanks.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To
Hi,
At my current gig we've been grappling with the same problem, and there
seems to be a solution in the 1.9.19 SDK release (finally!).
So my context is: my java frontend instances need to hit my elasticsearch
cluster hosted on GCE. The only way to reach the cluster was via a reverse
proxy ex
On Thu, May 7, 2015 at 11:39 AM, Ian Childress
wrote:
>
>
> On Thursday, May 7, 2015 at 2:25:08 PM UTC-4, Alex Martelli wrote:
>>
>> How so? Both GAE and GCE can be both talkers and listeners on Cloud
>> Pubsub topics / subscriptions (see https://cloud.google.com/pubsub/docs
>> ).
>>
>> I can't
On Thursday, May 7, 2015 at 2:25:08 PM UTC-4, Alex Martelli wrote:
>
> How so? Both GAE and GCE can be both talkers and listeners on Cloud
> Pubsub topics / subscriptions (see https://cloud.google.com/pubsub/docs
> ).
>
> I can't think of a good solution for taking many web requests and passi
On Thu, May 7, 2015 at 10:52 AM, Ian Childress
wrote:
> We (our Go dev team) want to connect our app engine apps to our compute
> engine apps directly using internal IP address. From my understanding
> through documentation and exhaustive searching, the solution is to use a
> public IP address. T
We (our Go dev team) want to connect our app engine apps to our compute
engine apps directly using internal IP address. From my understanding
through documentation and exhaustive searching, the solution is to use a
public IP address. This solution requires whitelisting an entire ip block
(Googl
