[google-appengine] Re: Authentication Integration with Google

[Pankaj Jha]

Thanks

On Monday, August 1, 2016 at 10:51:54 PM UTC+5:30, Nick (Cloud Platform 
Support) wrote:
>
> Hey Pankaj,
>
> As far as I know, we use exclusively OAuth2 in our auth systems, with no 
> explicit support for ActiveDirectory. If you can manage to read through the 
> documentation we provide about our auth systems and determine how that 
> integrates with your AD solution, this is certainly a possibility, although 
> it's not within my expertise to determine what that might look like, and 
> you're probably in a much better position to attempt to work from that 
> angle.
>
> What I can say is that if you want to provide secure access to the Cloud 
> Console, this is done through signing in to a Google account which has 
> permissions on the given project. 
>
> Sincerely,
>
> Nick
> Cloud Platform Community Support
>
> On Thursday, July 28, 2016 at 3:50:00 AM UTC-4, Pankaj Jha wrote:
>>
>>
>>
>> down votefavorite 
>> 
>>
>> I have a web application which works on windows active directory.Since it 
>> is deployed on Local IIS, windows authentications works fine. Now I am 
>> planning to move the authentication part of the application to cloud so 
>> that I can use AD users of multiple domain using OpenID connect(oAuth2). I 
>> am able to set OpenID connect to login using external user (using 
>> GoogleAuthentication) using email Id. My query is
>>
>> 1.Can I create my AD User to https://console.cloud.google.com ?
>>
>>1. Can I login my site using that User ?
>>2. Can cloud.google authenticate the user from my Active Directory?
>>
>> If anyone could guide me with some links that would be great.
>>
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/0c3496b9-77d4-43e8-a5f9-95e51ae63b10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Error for /dataflow org.xerial.snappy.SnappyError: [FAILED_TO_LOAD_NATIVE_LIBRARY] null

[Evan Jones]

You cannot use anything that uses JNI on App Engine. You'll have to see if 
you can configure this Snappy library to use a "pure Java" version, instead 
of trying to load a native library. See:

https://cloud.google.com/appengine/docs/java/runtime

On Wednesday, August 3, 2016 at 9:42:23 AM UTC-4, sudheer Aki wrote:
>
>
> Hi All,
>
>
>
> I am using pipeline code to read a file from Cloud storage.
>
>
>
> Code : 
>
>
> DataflowPipelineOptions options = 
> PipelineOptionsFactory.create().as(DataflowPipelineOptions.class);
> options.setRunner(BlockingDataflowPipelineRunner.class);
> options.setProject("projectId");
> options.setStagingLocation("StagingPath");
>
> //PipelineOptions options = PipelineOptionsFactory.create();
> // Then create the pipeline.
> Pipeline p = Pipeline.create(options);
> PCollection lines = 
> p.apply(TextIO.Read.named("ReadDataFromStorage").from("source_Path"));
>
>
> When am running from local eclipse am able to read a file.
>
> But when i deployed to App engine i am getting below error.I am using 
> snappy-java-1.1.2.1.jar.Please see the error below and help me ASAP.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Error for /dataflow org.xerial.snappy.SnappyError: 
> [FAILED_TO_LOAD_NATIVE_LIBRARY] null at 
> org.xerial.snappy.SnappyLoader.load(SnappyLoader.java:159) at 
> org.xerial.snappy.Snappy.(Snappy.java:47) at 
> org.xerial.snappy.SnappyOutputStream.(SnappyOutputStream.java:97) at 
> org.xerial.snappy.SnappyOutputStream.(SnappyOutputStream.java:89) at 
> org.xerial.snappy.SnappyOutputStream.(SnappyOutputStream.java:79) at 
> com.google.cloud.dataflow.sdk.util.SerializableUtils.serializeToByteArray(SerializableUtils.java:49)
>  
> at 
> com.google.cloud.dataflow.sdk.util.SerializableUtils.ensureSerializable(SerializableUtils.java:84)
>  
> at com.google.cloud.dataflow.sdk.io.Read$Bounded.(Read.java:108) at 
> com.google.cloud.dataflow.sdk.io.Read$Bounded.(Read.java:103) at 
> com.google.cloud.dataflow.sdk.io.Read.from(Read.java:62) at 
> com.google.cloud.dataflow.sdk.io.TextIO$Read$Bound.apply(TextIO.java:319)*
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2e349b5f-3eca-45b9-a5a9-52451a9ce823%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: appengine cloud sql performance issue ,taking too much time to process the request

[Christian F. Howes]

What are you doing with "large data"?  if you are loading large amounts of 
data into ram, processing it and then writing it back to the database it 
will be slower then smaller transactions.  There is a maximum read/write 
throughput and a max CPU speed on your DB and instances.

On Wednesday, August 3, 2016 at 9:23:52 PM UTC-7, ANOOP M.S wrote:
>
> No I haven't used Stackdriver , i will use now and update you. In my case 
> request processing works perfectly with small data, it has a problem when 
> its working with large data and manipulating it. any limitation for app 
> engine in handling large amount of data?
>
> On Thursday, August 4, 2016 at 2:11:03 AM UTC+5:30, Nicholas (Google Cloud 
> Support) wrote:
>>
>> Thanks for providing a little more information.  3 to 4 minutes is indeed 
>> strange but I cannot reproduce this latency.  For testing, I created 
>> 100,000 rows of text columns. Then sent over 100 requests to an App Engine 
>> instance that retrieves a single row (always the same one) and updates it. 
>>  I've had no issues getting these rows updated in under 1 or 2 seconds per 
>> request albeit with some contention issues since always reading/writing to 
>> the same row.
>>
>> To reiterate, I would need a lot more context to help your identify the 
>> source of the bottleneck.  Have you tried using Stackdriver Trace to 
>> identify what is taking the bulk of time to respond to a request?  Is it 
>> when processing the request, connecting to the DB, reading the row, writing 
>> to the row, closing the connection, compiling the response, any of the 
>> above?
>>
>> On Wednesday, July 27, 2016 at 4:39:29 AM UTC-4, ANOOP M.S wrote:
>>>
>>>
>>> 0down votefavorite 
>>> 
>>>
>>> on my django project i am using app-engine with cloud sql, the problem i 
>>> am facing a significant performance issue , app-engine is taking too much 
>>> time to process the request like 3,4 minutes, when i looked at the trace 
>>> its showing a latency below 1.5 seconds which was expected. my app-engine 
>>> is of F1 instance class Min Idle Instances, Max Idle Instances and Max 
>>> Concurrent Requests as auto, and cloud sql is a High memory machines with 
>>> 2CPU 13GB memory.
>>>
>>> and its happening even if i am the only user in the project, i don't 
>>> know where i am going wrong, how can i improve the perfomance?
>>>
>>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ec782708-1417-4fee-9cd4-986aec1d9e86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google Frontend inconsistent caching

[Christian F. Howes]

While we have not tried this with flexible runtimes, on standard GAE we are 
using cache-control, and pragma headers.  we do not use the vary header.  
while not documented the GAE support folks confirmed that google's caching 
proxy will not cache responses with certain values for the vary header 
(like custom headers and language headers), so you might try removing that 
from both systems.

also last i checked the cache was not guaranteed, and it's possible if your 
second app has low traffic that it's deemed not worth caching?  this area 
is a black box to me.

cfh

On Wednesday, August 3, 2016 at 4:34:11 PM UTC-7, Nick (Cloud Platform 
Support) wrote:
>
> Hey Matt,
>
> This is very interesting, and although I'd almost say it qualifies for a 
> post to the Public Issue Tracker, we can also discuss it here, since it's 
> somewhat broad, and it would be inconvenient to migrate all this info.
>
> Are you making your requests from behind any kind of proxy? This is 
> something which comes to mind. 
>
> I'll see if we can see anything from our end in the meantime.
>
> Cheers!
>
> Nick
> Cloud Platform Community Support
>
> On Monday, August 1, 2016 at 11:22:16 AM UTC-4, Matt Mohebbi wrote:
>>
>> I have a nodejs application I deploy to Appengine Flexible Environment 
>> via a docker custom runtime. When I deploy to one project (iodine-test), I 
>> get the great caching features of the Google Frontend:
>>
>> air:/tmp/plum/deploy-20160727-124350% curl -w 
>> "@/Users/matt/bin/curl-time-format.txt" -o /dev/null -s "
>> http://iodine-test.appspot.com/drug/zoloft"; -v
>>
>> *   Trying 216.58.194.209...
>>
>> * Connected to iodine-test.appspot.com (216.58.194.209) port 80 (#0)
>>
>> > GET /drug/zoloft HTTP/1.1
>>
>> > Host: iodine-test.appspot.com
>>
>> > User-Agent: curl/7.43.0
>>
>> > Accept: */*
>>
>> > 
>>
>> < HTTP/1.1 200 OK
>>
>> < Content-Type: text/html; charset=utf-8
>>
>> < ETag: W/"30a48-XHteNhi+a5i5072zCcVDyg"
>>
>> < Vary: Accept-Encoding
>>
>> < Via: irbk129:14580
>>
>> < X-Cloud-Trace-Context: 02917deaade7c823eed970361cd13ded;o=1
>>
>> < Date: Mon, 01 Aug 2016 15:15:49 GMT
>>
>> < Server: Google Frontend
>>
>> < Content-Length: 199240
>>
>> < Cache-Control: public, max-age=604800
>>
>> < Age: 7
>>
>> < 
>>
>> { [6754 bytes data]
>>
>> * Connection #0 to host iodine-test.appspot.com left intact
>>
>> time_namelookup:  0.004
>>
>>time_connect:  0.011
>>
>> time_appconnect:  0.000
>>
>>time_pretransfer:  0.011
>>
>>   time_redirect:  0.000
>>
>>  time_starttransfer:  0.023
>>
>> --
>>
>>  time_total:  0.048
>>
>>
>> However, when I deploy this same application to a different project 
>> (iodine-web-prod), caching doesn't occur on *any* of the requests, 
>> regardless of how often I request the same resource. 
>>
>>
>> air:/tmp/plum/deploy-20160727-124350% curl -w 
>> "@/Users/matt/bin/curl-time-format.txt" -o /dev/null -s "
>> http://iodine-web-prod.appspot.com/drug/zoloft"; -v
>>
>> *   Trying 216.58.195.241...
>>
>> * Connected to iodine-web-prod.appspot.com (216.58.195.241) port 80 (#0)
>>
>> > GET /drug/zoloft HTTP/1.1
>>
>> > Host: iodine-web-prod.appspot.com
>>
>> > User-Agent: curl/7.43.0
>>
>> > Accept: */*
>>
>> > 
>>
>> < HTTP/1.1 200 OK
>>
>> < Content-Type: text/html; charset=utf-8
>>
>> < Cache-Control: public, max-age=604800
>>
>> < ETag: W/"30a48-XHteNhi+a5i5072zCcVDyg"
>>
>> < Vary: Accept-Encoding
>>
>> < Via: iwer4:25789
>>
>> < X-Cloud-Trace-Context: fd82e108c58b92e3114028fdfcd22105;o=1
>>
>> < Date: Mon, 01 Aug 2016 15:16:46 GMT
>>
>> < Server: Google Frontend
>>
>> < Content-Length: 199240
>>
>> < 
>>
>> { [15256 bytes data]
>>
>> * Connection #0 to host iodine-web-prod.appspot.com left intact
>>
>> time_namelookup:  0.005
>>
>>time_connect:  0.010
>>
>> time_appconnect:  0.000
>>
>>time_pretransfer:  0.010
>>
>>   time_redirect:  0.000
>>
>>  time_starttransfer:  1.503
>>
>> --
>>
>>  time_total:  1.536
>>
>>
>> I've combed through the bits and pieces of unofficial documentation:
>>
>>
>> https://code.google.com/p/googleappengine/issues/detail?id=2258
>>
>>
>> https://web.archive.org/web/20110826081218/http://www.kyle-jensen.com/proxy-caching-on-google-appengine
>>
>>
>> https://groups.google.com/forum/#!topic/google-appengine/6xAV2Q5x8AU/discussion
>>
>>
>> And also reviewed the documentation for Google Cloud CDN assuming that 
>> the policies outlined there are the same as those applied to Appengine. 
>>
>>
>> https://cloud.google.com/cdn/docs/caching
>>
>>
>> However, nothing explains why I would be getting this inconsistent 
>> behavior between projects. Any ideas?
>>
>

-- 
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@go

[google-appengine] Performance is *way* too slow with pubsub push -> app engine.

[Garrett Hunyadi]

Hi.  I have a requirement to process ~20k calls per second. My system 
processes lists of ~1M entries and performs multiple jobs for each item. 
 It is very “bursty” in nature as it isn’t always processing a list.  I 
added a App Engine flex env (with Rails), using automatic scaling, with an 
test endpoint to wait 5 seconds and return.   I push to the pubsub topic 
and a push subscription sends to App Engine.   Running this hits a steady 
state of 20-30 requests per second.  


I guessed that the problem was the interaction of the pubsub push volume 
algorithm interacting with the App Engine, but then I ran a second test 
where I just blasted curl requests as in a loop with multiple processes. 
 This also ran at 20-30 rps.  


I’m stuck at this point and wondering how to proceed. How can I configure 
the system for higher performance? I need a performance of three orders of 
magnitude from what I see.


Thanks so much for helping! 


-garrett

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a736d50b-efa0-4f18-a72e-e4b207f0f67c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google Frontend inconsistent caching

[Matt Mohebbi]

Hi Nick,

Happy to move this over to the Public Issue tracker if you like. Should I
start a new bug or post on the existing one regarding lack of documentation?

The proxy point is an interesting one. We were thinking the same thing
(both my home and work use Webpass for internet) but when I try this
through the cloud shell, I get the same result.

It is also worth noting that as a test, we built a stack using Google
Compute Engine and the HTTP load balancer with the Google Cloud CDN
enabled. There we see the same results as the iodine-test appengine
instance: consistent caching behavior of the Google Frontend.

This is a really strange bug. Would love to get to the bottom of it as we'd
prefer to use Appengine. Let me know if you dig up anything on your end!

Thanks,
Matt

On Wed, Aug 3, 2016 at 4:34 PM, 'Nick (Cloud Platform Support)' via Google
App Engine  wrote:

> Hey Matt,
>
> This is very interesting, and although I'd almost say it qualifies for a
> post to the Public Issue Tracker, we can also discuss it here, since it's
> somewhat broad, and it would be inconvenient to migrate all this info.
>
> Are you making your requests from behind any kind of proxy? This is
> something which comes to mind.
>
> I'll see if we can see anything from our end in the meantime.
>
> Cheers!
>
> Nick
> Cloud Platform Community Support
>
>
> On Monday, August 1, 2016 at 11:22:16 AM UTC-4, Matt Mohebbi wrote:
>>
>> I have a nodejs application I deploy to Appengine Flexible Environment
>> via a docker custom runtime. When I deploy to one project (iodine-test), I
>> get the great caching features of the Google Frontend:
>>
>> air:/tmp/plum/deploy-20160727-124350% curl -w
>> "@/Users/matt/bin/curl-time-format.txt" -o /dev/null -s "
>> http://iodine-test.appspot.com/drug/zoloft"; -v
>>
>> *   Trying 216.58.194.209...
>>
>> * Connected to iodine-test.appspot.com (216.58.194.209) port 80 (#0)
>>
>> > GET /drug/zoloft HTTP/1.1
>>
>> > Host: iodine-test.appspot.com
>>
>> > User-Agent: curl/7.43.0
>>
>> > Accept: */*
>>
>> >
>>
>> < HTTP/1.1 200 OK
>>
>> < Content-Type: text/html; charset=utf-8
>>
>> < ETag: W/"30a48-XHteNhi+a5i5072zCcVDyg"
>>
>> < Vary: Accept-Encoding
>>
>> < Via: irbk129:14580
>>
>> < X-Cloud-Trace-Context: 02917deaade7c823eed970361cd13ded;o=1
>>
>> < Date: Mon, 01 Aug 2016 15:15:49 GMT
>>
>> < Server: Google Frontend
>>
>> < Content-Length: 199240
>>
>> < Cache-Control: public, max-age=604800
>>
>> < Age: 7
>>
>> <
>>
>> { [6754 bytes data]
>>
>> * Connection #0 to host iodine-test.appspot.com left intact
>>
>> time_namelookup:  0.004
>>
>>time_connect:  0.011
>>
>> time_appconnect:  0.000
>>
>>time_pretransfer:  0.011
>>
>>   time_redirect:  0.000
>>
>>  time_starttransfer:  0.023
>>
>> --
>>
>>  time_total:  0.048
>>
>>
>> However, when I deploy this same application to a different project
>> (iodine-web-prod), caching doesn't occur on *any* of the requests,
>> regardless of how often I request the same resource.
>>
>>
>> air:/tmp/plum/deploy-20160727-124350% curl -w
>> "@/Users/matt/bin/curl-time-format.txt" -o /dev/null -s "
>> http://iodine-web-prod.appspot.com/drug/zoloft"; -v
>>
>> *   Trying 216.58.195.241...
>>
>> * Connected to iodine-web-prod.appspot.com (216.58.195.241) port 80 (#0)
>>
>> > GET /drug/zoloft HTTP/1.1
>>
>> > Host: iodine-web-prod.appspot.com
>>
>> > User-Agent: curl/7.43.0
>>
>> > Accept: */*
>>
>> >
>>
>> < HTTP/1.1 200 OK
>>
>> < Content-Type: text/html; charset=utf-8
>>
>> < Cache-Control: public, max-age=604800
>>
>> < ETag: W/"30a48-XHteNhi+a5i5072zCcVDyg"
>>
>> < Vary: Accept-Encoding
>>
>> < Via: iwer4:25789
>>
>> < X-Cloud-Trace-Context: fd82e108c58b92e3114028fdfcd22105;o=1
>>
>> < Date: Mon, 01 Aug 2016 15:16:46 GMT
>>
>> < Server: Google Frontend
>>
>> < Content-Length: 199240
>>
>> <
>>
>> { [15256 bytes data]
>>
>> * Connection #0 to host iodine-web-prod.appspot.com left intact
>>
>> time_namelookup:  0.005
>>
>>time_connect:  0.010
>>
>> time_appconnect:  0.000
>>
>>time_pretransfer:  0.010
>>
>>   time_redirect:  0.000
>>
>>  time_starttransfer:  1.503
>>
>> --
>>
>>  time_total:  1.536
>>
>>
>> I've combed through the bits and pieces of unofficial documentation:
>>
>>
>> https://code.google.com/p/googleappengine/issues/detail?id=2258
>>
>> https://web.archive.org/web/20110826081218/http://www.kyle-
>> jensen.com/proxy-caching-on-google-appengine
>>
>> https://groups.google.com/forum/#!topic/google-appengine/
>> 6xAV2Q5x8AU/discussion
>>
>>
>> And also reviewed the documentation for Google Cloud CDN assuming that
>> the policies outlined there are the same as those applied to Appengine.
>>
>>
>> https://cloud.google.com/cdn/docs/caching
>>
>>
>> However, nothing explains why I would be getting this inconsistent
>> behavior between projects. Any ideas?
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Go

Re: [google-appengine] Re: Google Frontend inconsistent caching

[Matt Mohebbi]

Hi Christian,

Thanks for the response. Yes, we have read about the Google Frontend being
picky about Vary params (I imagine they don't want people blowing through
their cache by putting dumb things in there). As a result, we are only
sending vary for content type.

And what's odd is that the same code running in two different appengine
projects give different behavior (and this has been consistent now for two
weeks!). As I mentioned before, we also pushed the same code to GCE +
Google Cloud CDN and it works just fine there too.

My understanding is that the cache is not guaranteed but what's odd is that
both projects are for testing are are hardly used (despite the name,
iodine-web-prod is not in use until we can figure out this bug!).

-matt

On Thu, Aug 4, 2016 at 12:07 PM, Christian F. Howes <
christian.ho...@starmakerinteractive.com> wrote:

> While we have not tried this with flexible runtimes, on standard GAE we
> are using cache-control, and pragma headers.  we do not use the vary
> header.  while not documented the GAE support folks confirmed that google's
> caching proxy will not cache responses with certain values for the vary
> header (like custom headers and language headers), so you might try
> removing that from both systems.
>
> also last i checked the cache was not guaranteed, and it's possible if
> your second app has low traffic that it's deemed not worth caching?  this
> area is a black box to me.
>
> cfh
>
>
> On Wednesday, August 3, 2016 at 4:34:11 PM UTC-7, Nick (Cloud Platform
> Support) wrote:
>>
>> Hey Matt,
>>
>> This is very interesting, and although I'd almost say it qualifies for a
>> post to the Public Issue Tracker, we can also discuss it here, since it's
>> somewhat broad, and it would be inconvenient to migrate all this info.
>>
>> Are you making your requests from behind any kind of proxy? This is
>> something which comes to mind.
>>
>> I'll see if we can see anything from our end in the meantime.
>>
>> Cheers!
>>
>> Nick
>> Cloud Platform Community Support
>>
>> On Monday, August 1, 2016 at 11:22:16 AM UTC-4, Matt Mohebbi wrote:
>>>
>>> I have a nodejs application I deploy to Appengine Flexible Environment
>>> via a docker custom runtime. When I deploy to one project (iodine-test), I
>>> get the great caching features of the Google Frontend:
>>>
>>> air:/tmp/plum/deploy-20160727-124350% curl -w
>>> "@/Users/matt/bin/curl-time-format.txt" -o /dev/null -s "
>>> http://iodine-test.appspot.com/drug/zoloft"; -v
>>>
>>> *   Trying 216.58.194.209...
>>>
>>> * Connected to iodine-test.appspot.com (216.58.194.209) port 80 (#0)
>>>
>>> > GET /drug/zoloft HTTP/1.1
>>>
>>> > Host: iodine-test.appspot.com
>>>
>>> > User-Agent: curl/7.43.0
>>>
>>> > Accept: */*
>>>
>>> >
>>>
>>> < HTTP/1.1 200 OK
>>>
>>> < Content-Type: text/html; charset=utf-8
>>>
>>> < ETag: W/"30a48-XHteNhi+a5i5072zCcVDyg"
>>>
>>> < Vary: Accept-Encoding
>>>
>>> < Via: irbk129:14580
>>>
>>> < X-Cloud-Trace-Context: 02917deaade7c823eed970361cd13ded;o=1
>>>
>>> < Date: Mon, 01 Aug 2016 15:15:49 GMT
>>>
>>> < Server: Google Frontend
>>>
>>> < Content-Length: 199240
>>>
>>> < Cache-Control: public, max-age=604800
>>>
>>> < Age: 7
>>>
>>> <
>>>
>>> { [6754 bytes data]
>>>
>>> * Connection #0 to host iodine-test.appspot.com left intact
>>>
>>> time_namelookup:  0.004
>>>
>>>time_connect:  0.011
>>>
>>> time_appconnect:  0.000
>>>
>>>time_pretransfer:  0.011
>>>
>>>   time_redirect:  0.000
>>>
>>>  time_starttransfer:  0.023
>>>
>>> --
>>>
>>>  time_total:  0.048
>>>
>>>
>>> However, when I deploy this same application to a different project
>>> (iodine-web-prod), caching doesn't occur on *any* of the requests,
>>> regardless of how often I request the same resource.
>>>
>>>
>>> air:/tmp/plum/deploy-20160727-124350% curl -w
>>> "@/Users/matt/bin/curl-time-format.txt" -o /dev/null -s "
>>> http://iodine-web-prod.appspot.com/drug/zoloft"; -v
>>>
>>> *   Trying 216.58.195.241...
>>>
>>> * Connected to iodine-web-prod.appspot.com (216.58.195.241) port 80 (#0)
>>>
>>> > GET /drug/zoloft HTTP/1.1
>>>
>>> > Host: iodine-web-prod.appspot.com
>>>
>>> > User-Agent: curl/7.43.0
>>>
>>> > Accept: */*
>>>
>>> >
>>>
>>> < HTTP/1.1 200 OK
>>>
>>> < Content-Type: text/html; charset=utf-8
>>>
>>> < Cache-Control: public, max-age=604800
>>>
>>> < ETag: W/"30a48-XHteNhi+a5i5072zCcVDyg"
>>>
>>> < Vary: Accept-Encoding
>>>
>>> < Via: iwer4:25789
>>>
>>> < X-Cloud-Trace-Context: fd82e108c58b92e3114028fdfcd22105;o=1
>>>
>>> < Date: Mon, 01 Aug 2016 15:16:46 GMT
>>>
>>> < Server: Google Frontend
>>>
>>> < Content-Length: 199240
>>>
>>> <
>>>
>>> { [15256 bytes data]
>>>
>>> * Connection #0 to host iodine-web-prod.appspot.com left intact
>>>
>>> time_namelookup:  0.005
>>>
>>>time_connect:  0.010
>>>
>>> time_appconnect:  0.000
>>>
>>>time_pretransfer:  0.010
>>>
>>>   time_redirect:  0.000
>>>
>>>  time_starttransfer:  1.503
>>>
>>> --

[google-appengine] Full Stack .Net Developer || Santa Clara,CA

[rahul goswami]

Hi

Please share profile at nav...@techone-staffing.com

*Full Stack .NET Developer*
*Location: Santa Clara, CA*
*Duration: 6 months*

We are looking for Senior .Net developers with minimum 10 years of industry
experience in the following.
Experience with large scale projects with multiple touch points.
Requirement gathering and analysis.
Extremely detailed oriented.
Ability to work with external teams and resolve road blocks.
Strong experience developing ASP.NET MVC applications, SPA, responsive UI.
Senior level experience in .Net, Entity Framework, SQL server platform.
Strong JavaScript skills and experience utilizing frontend UI frameworks
(bootstrap, Angular JS, Ember JS, etc.)
Have an eye for visual layout, design, CSS3.
Experience in Kendo UI preferred

Tasks
The tasks for the Senior .NET Developer include, but not limited to, the
following:
Provide Development support for the Data Mart and back office Projects
Lead other software engineers to design and implement well-integrated
products
Define and evolve the architecture for the system.
Expert in all technical aspects of the product
Evaluate and recommend appropriate technologies based on product needs and
industry trends
Develop creative solutions and write technical design & architecture
documents
Provide work estimates for proposed projects
Cross-train developers on product features that are implemented
Constantly look for better processes for projecting and improving project
profitability
Perform hands-on software design and development in .NET
Develop and execute unit tests for product components
Establish architectural standards and best practices
Encourage innovation of process and creative development methodologies
Work closely with management to determine feasibility of product features
Establish standards and Perform peer code reviews and provide feedback
Promote high quality, scalability, and timely completion of project

*Must-Have Technical Knowledge and Skills*
Senior .Net Developer shall possess 7+ years technical knowledge and
experience with most of the following systems, platforms, applications, and
skills:
BS or MS in Computer Science or equivalent degree
7+ years of software development experience
3+ years of proven technical lead and architect experience
Proficient in ASP.NET as well as ASP.NET MVC web frameworks
Experienced with C#, Javascript, JQuery, AJAX, HTML, and CSS
Development experience in an enterprise-class system with multi-tier
architecture
Must have .NET Web application architecture, design, & development
experience
Broad experience with .NET Framework 3.5 or above including WPF, WCF, & WF
Expert in ASP.NET MVC, Web Forms, & Entity Framework
Expert in ADO.NET / WFC Data Services and familiar with LINQ
Expert with Design patterns, SOA design & web service development
Strong experience in developing for high-availability clustered environments
Working knowledge of Linux and Windows
Strong communication and writing skills
Comfortable working in a flexible Agile development environment
Solid understanding of data warehouse concepts, data-marts & MDM.
Should be able to write reports using various reports generation tools and
languages
Custom development utilizing Microsoft SharePoint, BizTalk, SSAS, SSIS,
SSRS, MDM, and DQS will be a plus
Expert knowledge of SQL statements
Prior experience in the insurance industry is a plus
Microsoft certifications desirable




*Thanks & Regards*
*Naveen Kumar*
*TechOne*
*7901 Stoneridge Dr, #403*
*Pleasanton, CA 94588*
*732.230.4292*
*nav...@techone-staffing.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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAA0vNTGkGT6Y3EtAV%2BfJ3XCGoOwXPNFkwHRyrsyKKgVVq8iunA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Share your thoughts with the Google App Engine team!

['Alison Kather' via Google App Engine]

We are looking for people who are using App Engine to give us some insight 
into how they are monitoring and debugging their applications.

If this sounds like you and you have some time to share your thoughts, 
please fill out this survey. You will be helping our App Engine team 
immensely as we plan for future product enhancements and new features.

Take the Survey Now 



-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9c975b63-6c1e-4b0a-b1ac-ccdd82c461f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Bizarre Panic on NewKey

[Robbie McKinstry]

Hey all,

TL; DR Can someone help explain why this code 
 
panics?

I'm an experienced Go developer trying to write a single entity to 
datastore in Go. Many of the tutorials are out of date (using the 
appengine.Context type instead of the net/context.Context type). For 
example, the official example code 

 
is out of date. However, once I updated the code, I had a weird and 
unintuitive panic from my call to NewKey(). For whatever reason, it appears 
that the call to google.golang.org/appengine/internal.fullyQualifiedAppID() 
panics. 
Well, I scrapped that code and tried a different tutorial.

I tried this tutorial 
 and 
updated the code to use to correct context. I also scrapped all of the code 
that doesn't simply write to the database. That left me with this tiny 
skeleton here 
.
Still, oddly, I get the same bug! The exact same stack trace, except with a 
call to NewIncompleteKey() resulting in the panic instead of a call to 
NewKey() resulting in the panic.

I've spent too many hours trying to figure out this simple program, even 
digging through the app engine library's source code. Any help would be 
appreciated!

- Robbie McKinstry

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fba97232-b4cd-415a-a994-0d05f8273071%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Ignoring invalid login cookie: true

[NP]

 

Hello,


Since upgrading to GAE release: "1.9.40", I now the see entry below in my 
log console (development server)


>>> WARNING  2016-08-05 05:04:05,754 login.py:99] Ignoring invalid 
login cookie: true <<


This wasn't showing up before I did the migration to 1.9.40. Anybody know 
what this means?


I searched for login.py (this is an app engine file) and I couldn't find 
the message in the file


-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c3856264-e3c7-4bdf-9f4c-71f3afe1a02c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] About bc.googleusercontent.com domain

[Ken Walker]

Hello,

We are receiving many requests to our server from bc.googleusercontent.com 
and user agent doesn't include APP Engine information so please clear my 
couple of doubts that as mention like below

1) Is that app engine IP or compute engine IP ?
2) what does "bc" mean in bc.googleusercontent.com ?

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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/bfb36325-2776-4620-8f1a-a526abde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Ignoring invalid login cookie: true

[NP]

In addition, I just noticed that I can't sign in again as administrator in 
development server for URLs that were secured in app.yaml using #  login: 
admin

Previously, I would get a popup with email - t...@example.com and a 
checkbox saying 'sign in as administrator' and ticking this would emulate 
my signing in as an administrator. This is no longer working

On Thursday, August 4, 2016 at 10:18:28 PM UTC-7, NP wrote:
>
> Hello,
>
>
> Since upgrading to GAE release: "1.9.40", I now the see entry below in my 
> log console (development server)
>
>
> >>> WARNING  2016-08-05 05:04:05,754 login.py:99] Ignoring invalid 
> login cookie: true <<
>
>
> This wasn't showing up before I did the migration to 1.9.40. Anybody know 
> what this means?
>
>
> I searched for login.py (this is an app engine file) and I couldn't find 
> the message in the file
>
>
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/669cc08c-736c-491f-8863-c6a5d485ae44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.