Timeline for Google App Engine [app]s - We are all on the same quota!
Current License: CC BY-SA 2.5
24 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
| Sep 5, 2011 at 4:47 | comment | added | Nick Johnson | @systempuntoout I'm positive - it's always been the case that although you can set part of the user-agent string, you can't remove your App ID from it. | |
| Jan 5, 2011 at 13:26 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 126 characters in body; added 1 characters in body
|
| Nov 22, 2010 at 13:41 | comment | added | systempuntoout | @Nick are you sure? AFAIK user-agent can be set since SDK version 1.2.1 . I remember this because I auto answered my own question on this topic 7 month ago here | |
| Oct 28, 2010 at 15:15 | comment | added | Nick Johnson | For reference, we (App Engine) include the App ID in the user-agent header, and we don't let users set the user-agent header on outgoing requests. If the IP comes from our pool (_netblocks.google.com), you can trust that the App ID in the user-agent is accurate. | |
| Oct 22, 2010 at 11:16 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 6 characters in body; edited body; added 1 characters in body
|
| Oct 22, 2010 at 11:10 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 1 characters in body; added 8 characters in body
|
| Oct 22, 2010 at 11:05 | vote | accept | systempuntoout | ||
| Oct 22, 2010 at 11:02 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 2736 characters in body; added 2 characters in body
|
| Oct 20, 2010 at 20:33 | answer | added | Vladyslav Tserman | timeline score: 2 | |
| Oct 20, 2010 at 18:36 | answer | added | Kevin Montrose | timeline score: 6 | |
| Oct 20, 2010 at 17:46 | answer | added | badp | timeline score: 2 | |
| Oct 20, 2010 at 17:17 | comment | added | Sky Sanders | DOOOOOOOOOOOOOOOOMED! | |
| Oct 20, 2010 at 15:02 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 59 characters in body; edited body
|
| Oct 20, 2010 at 14:57 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 151 characters in body
|
| Oct 20, 2010 at 13:45 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 2 characters in body
|
| Oct 20, 2010 at 12:13 | answer | added | Sky Sanders | timeline score: 5 | |
| Oct 20, 2010 at 10:12 | answer | added | Shay Erlichmen | timeline score: 1 | |
| Oct 20, 2010 at 9:53 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 49 characters in body
|
| Oct 20, 2010 at 9:48 | comment | added | systempuntoout | @Vladislav I totally agree that a cloud platform can't be whitelisted! But Twitter offers a way to bypass this problem using authenticated requests per app and/or user. | |
| Oct 20, 2010 at 9:43 | comment | added | Vladyslav Tserman | I Have no big hopes that this issue would be resolved anytime soon. Even Twitter claims that the majority of cloud platforms, including Google App Engine, cannot be whitelisted to access their Search API due to absence of static IP. But I continue to hope that something would be done. | |
| Oct 20, 2010 at 9:21 | history | edited | systempuntoout | CC BY-SA 2.5 |
added 4 characters in body
|
| Oct 20, 2010 at 8:52 | history | edited | systempuntoout | CC BY-SA 2.5 |
edited title
|
| Oct 20, 2010 at 8:35 | history | asked | systempuntoout | CC BY-SA 2.5 |