Thanks for giving me a chance to explain this.
Previously we were not accounting of all the "cached" requests coming
to applications through www.customdomain.com, meaning that the admin
console was missing some portion of the cached requests (cache hits),
and was mostly only billing non-cached request (cache misses).
That caused applications serving from appid.appspot.com to be billed
more than application serving from www.customdomain.com:
- serving cached requests from www.customdomain.com was basically free
(not billed)
- serving cached requests from appid.appspot.com was billed.
We recently fixed this, and now the admin console (and the bill)
should reflect all the cached requests coming to applications
regardless of if they are coming from www.customdomain.com or
appid.appspot.com.
Hope this explanation make things clearer.
> --
> 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-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>
--
Johan Euphrosine (proppy)
Developer Programs Engineer
Google Developer Relations
Yep, cached request as in HTTP Cached request:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html
Hope this is more clear now.
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/ZlOWtP673FEJ.