RE: RE: [google-appengine] HR Issues (But Up time is great)

2011-03-24 Thread Brandon Wirtz
Looks like HR now has Dash board details going back 36 hours.. Not great.
But better. Hoping this means that in 72 hours we will have data going back
72 hours :-)

 



 

From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Simon Knott
Sent: Tuesday, March 22, 2011 2:38 AM
To: google-appengine@googlegroups.com
Cc: Brandon Wirtz
Subject: Re: RE: [google-appengine] HR Issues (But Up time is great)

 

I'm glad to hear it's now working for you!

-- 
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

<>

Re: [google-appengine] HR Issues (But Up time is great)

2011-03-22 Thread Ikai Lan (Google)
Good to hear it's working. If I hear anything about what changed, I'll let
you guys know.

Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: http://www.reddit.com/r/appengine



On Mon, Mar 21, 2011 at 7:33 PM, Brandon Wirtz  wrote:

> I swear someone cheated... Or ran over and flipped a switch when I asked...
> Cause out of the same tool, now I get
>
> HTTP/1.1 200 OK
> Via: HTTP/1.1 GWA (remote cache hit)
> Accept-Ranges: bytes
> Last-Modified: Wed, 02 Mar 2011 01:25:48 GMT
> Etag: "159827d-169b0-49d75caeb5f00"
> Content-Type: image/png
> Age: 6985
> Cache-Control: public; max-age=300
> Date: Tue, 22 Mar 2011 02:29:27 GMT
> Server: Google Frontend
> Content-Length: 92592
>
>
> Which even says that Google gave me a cache hit.  Which is interesting
> cause
> the Dashboard on the app doesn't claim it has any of those. (even though My
> MS version of the app does)
>
> So just ignore me, it seems to work well enough,  I'm just partially
> insane.
> :-)
>
>
>
>
>
> -Original Message-
> From: google-appengine@googlegroups.com
> [mailto:google-appengine@googlegroups.com] On Behalf Of Stephen
> Sent: Monday, March 21, 2011 3:54 PM
> To: google-appengine@googlegroups.com
> Subject: Re: [google-appengine] HR Issues (But Up time is great)
>
> On Sat, Mar 19, 2011 at 8:32 PM, Brandon Wirtz 
> wrote:
> >
> > 1. Caching doesn’t work, and because of the way headers are
> >forced to be set all requests expire immediately so the user won’t
> cache either.
> >
> > (Headers from a request)
> >
> > HTTP/1.1 405 Method Not Allowed
> > Content-Type: text/html; charset=utf-8
> > Cache-Control: no-cache, must-revalidate
> > Expires: Fri, 01 Jan 1990 00:00:00 GMT
> > Set-Cookie: S=apphosting=5hoCHm4x9c3ZrrxQEN5Q4A; path=/
> > Date: Sat, 19 Mar 2011 19:37:21 GMT
> > Pragma: no-cache
> > Server: Google Frontend
> > Content-Length: 0
>
>
> These look like headers from a response, not a request, and the response
> code is 405: Method Not Allowed. ie. the request was something other than a
> GET, POST, PUT or DELETE, in which case you might expect the error response
> to force a no-cache header.
>
> Are you sure your test is accurate?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: RE: [google-appengine] HR Issues (But Up time is great)

2011-03-22 Thread Simon Knott
I'm glad to hear it's now working for you!

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



RE: [google-appengine] HR Issues (But Up time is great)

2011-03-21 Thread Brandon Wirtz
I swear someone cheated... Or ran over and flipped a switch when I asked...
Cause out of the same tool, now I get  

HTTP/1.1 200 OK
Via: HTTP/1.1 GWA (remote cache hit)
Accept-Ranges: bytes
Last-Modified: Wed, 02 Mar 2011 01:25:48 GMT
Etag: "159827d-169b0-49d75caeb5f00"
Content-Type: image/png
Age: 6985
Cache-Control: public; max-age=300
Date: Tue, 22 Mar 2011 02:29:27 GMT
Server: Google Frontend
Content-Length: 92592


Which even says that Google gave me a cache hit.  Which is interesting cause
the Dashboard on the app doesn't claim it has any of those. (even though My
MS version of the app does)

So just ignore me, it seems to work well enough,  I'm just partially insane.
:-)





-Original Message-
From: google-appengine@googlegroups.com
[mailto:google-appengine@googlegroups.com] On Behalf Of Stephen
Sent: Monday, March 21, 2011 3:54 PM
To: google-appengine@googlegroups.com
Subject: Re: [google-appengine] HR Issues (But Up time is great)

On Sat, Mar 19, 2011 at 8:32 PM, Brandon Wirtz  wrote:
>
> 1. Caching doesn’t work, and because of the way headers are
>forced to be set all requests expire immediately so the user won’t
cache either.
>
> (Headers from a request)
>
> HTTP/1.1 405 Method Not Allowed
> Content-Type: text/html; charset=utf-8
> Cache-Control: no-cache, must-revalidate
> Expires: Fri, 01 Jan 1990 00:00:00 GMT
> Set-Cookie: S=apphosting=5hoCHm4x9c3ZrrxQEN5Q4A; path=/
> Date: Sat, 19 Mar 2011 19:37:21 GMT
> Pragma: no-cache
> Server: Google Frontend
> Content-Length: 0


These look like headers from a response, not a request, and the response
code is 405: Method Not Allowed. ie. the request was something other than a
GET, POST, PUT or DELETE, in which case you might expect the error response
to force a no-cache header.

Are you sure your test is accurate?

--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.



Re: [google-appengine] HR Issues (But Up time is great)

2011-03-21 Thread Stephen
On Sat, Mar 19, 2011 at 8:32 PM, Brandon Wirtz  wrote:
>
> 1. Caching doesn’t work, and because of the way headers are
>forced to be set all requests expire immediately so the user won’t cache 
> either.
>
> (Headers from a request)
>
> HTTP/1.1 405 Method Not Allowed
> Content-Type: text/html; charset=utf-8
> Cache-Control: no-cache, must-revalidate
> Expires: Fri, 01 Jan 1990 00:00:00 GMT
> Set-Cookie: S=apphosting=5hoCHm4x9c3ZrrxQEN5Q4A; path=/
> Date: Sat, 19 Mar 2011 19:37:21 GMT
> Pragma: no-cache
> Server: Google Frontend
> Content-Length: 0


These look like headers from a response, not a request, and the
response code is 405: Method Not Allowed. ie. the request was
something other than a GET, POST, PUT or DELETE, in which case you
might expect the error response to force a no-cache header.

Are you sure your test is accurate?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.