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
The ability to specify the network for a Managed VM is huge! Thank you!
Goodbye unnecessary public-exposed proxies!
On Thursday, April 16, 2015 at 2:28:51 PM UTC-4, Sarah Murphy wrote:
*Java*
- appcfg now outputs a warning if OAuth2 is not used for authentication
- When deploying or
I just need to wail about this:
My App Engine/Java app hits my Elasticsearch cluster hosted on GCE, using
URLFetch. The Elasticsearch queries themselves execute under 10ms. The
response coming back to App Engine typically takes 120ms. The Elasticsearch
cluster is fronted by reverse proxy
Sorry, my bad. I was setting the handler's http response status to 204,
which seemed to be messing up blobstore service. Setting the handler's
response status to 200 fixes blobstore downloads.
On Friday, February 13, 2015 at 9:49:47 PM UTC-5, Hussein Vastani wrote:
Hi all,
I have a java
Hi all,
I have a java app engine application thats under development, currently
running on v 1.9.17.
Since this afternoon (Fri Feb 13, 2015), any attempts to download blobs
with a blobKey (as described in the docs
https://cloud.google.com/appengine/docs/java/blobstore/#Java_Serving_a_blob)
Hi all,
I'm wondering if this is possible: I'd like to use a (secured) backend
Managed VM to act as a load balancing reverse proxy to a cluster of GCE VMs
hosting ElasticSearch. So the ES cluster VMs will not have public internet
IPs and the managed VM accesses the Elasticsearch VMs using their
