[google-appengine] Re: Google auth default credentials for GAE standard 2nd Gen (Python)

[Eric G]

It was more a question because the documentation was unclear for 2nd 
generation standard GAE environments.  
I have no problem using an explicit credentials file - in fact I prefer 
that to the magic of default credentials, and using the GCE metadata 
service involves an extra network hop if I'm not mistaken.

On Tuesday, September 25, 2018 at 4:50:57 PM UTC-4, Stewart Reichling wrote:
>
> Hi Eric -- can you follow up with more details about your use case?
>
> On Tuesday, September 18, 2018 at 10:02:24 AM UTC-7, Eric G wrote:
>>
>> Thanks!  I think I will stick with using an explicit service account json 
>> file, but it's good to know this route works.
>>
>> On Monday, September 17, 2018 at 3:43:43 PM UTC-4, David (Google Cloud 
>> Support) wrote:
>>>
>>> Python 3.7 on App Engine standard provides the GCE metadata service, so 
>>> as an alternative, you could use Compute Engine Credentials 
>>> <https://cloud.google.com/docs/authentication/production#auth-cloud-compute-engine-python>.
>>>  
>>> I will inform our documentation team to update this document since it is 
>>> outdated and it does not include App Engine Standard Second Generation as 
>>> one of the platforms where you could use these credentials.
>>>
>>

-- 
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/e46520e4-b680-422b-baec-6b983145043b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Second gen GAE Python 3.7 > Cloud SQL - MySQL

[Eric G]

No problem, thanks for your work.

On Monday, September 17, 2018 at 11:47:22 AM UTC-4, Steren Giannini wrote:
>
> Hi,
> Yes GAE second generation expose a /cloudsql socket to access Cloud SQL. 
> Sorry about the lack of docs, we are in the process of (better) documenting 
> it.
>
> Steren
> Product Manager
>
> On Sun, Sep 16, 2018 at 7:11 AM rahulrv via Google App Engine <
> google-a...@googlegroups.com > wrote:
>
>> You should be able to use any library which works with mysql or postgres 
>> to connect using the unix socket /cloudsql/
>>
>>
>> On Wednesday, September 12, 2018 at 8:00:08 AM UTC-7, Eric G wrote:
>>>
>>> Thanks for this. The second link is to the flex environment 
>>> documentation. Are you saying that App Engine standard 2nd gen uses the 
>>> same method of connecting to CloudSQL instances as flex, i.e. via the unix 
>>> socket  /cloudsql/INSTANCE_CONNECTION_NAME ?  If so, it would be 
>>> helpful to have those instructions/example on the first link (to standard 
>>> 2nd gen) as well.
>>>
>>> Personally, I would like to see an example that doesn't depend on 
>>> SQLAlchemy + Flask, otherwise people may think they have to use those. I 
>>> guess it's not hard to figure out but just some acknowledgement that you 
>>> can set your own environment variables and manually use them to connect 
>>> with pymysql or whatever adapter.
>>>
>>>
>>> On Tuesday, September 11, 2018 at 11:22:24 PM UTC-4, Olu wrote:
>>>>
>>>> There are different ways to connect to the CloudSQL instance depending 
>>>> on the location from where you are connecting. If you are connecting from 
>>>> an App Engine instance which is located in a project which is different 
>>>> from the project which the CloudSQL instance resides, you must use a 
>>>> service account to allow connection between the App Engine application and 
>>>> the Cloud SQL as described in the link 
>>>> <https://cloud.google.com/appengine/docs/standard/python3/using-cloud-sql#granting_access_to_gae_name_short>
>>>> .
>>>>
>>>> However, when connecting from your App Engine Application within the 
>>>> same project, you simply have to configure your app.yaml with the user, 
>>>> password, database, and instance connection name variables from Cloud SQL, 
>>>> See the documentation 
>>>> <https://cloud.google.com/appengine/docs/flexible/python/using-cloud-sql#setting_connection_strings_and_adding_a_library>
>>>> . 
>>>>
>>>> External applications have to connect to the Cloud SQL instances 
>>>> directly through the public IP address and the IP addresses of the 
>>>> connecting application have to be white listed in the Cloud SQL instance 
>>>> on 
>>>> the Authorization Tab of the Instance page.
>>>>
>>>>
>>>> -- 
>> 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-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@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/469db80a-f980-4468-b56e-138eb5b6e731%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/469db80a-f980-4468-b56e-138eb5b6e731%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/89e99ac8-bb12-415c-906a-db9935671325%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google auth default credentials for GAE standard 2nd Gen (Python)

[Eric G]

Thanks!  I think I will stick with using an explicit service account json 
file, but it's good to know this route works.

On Monday, September 17, 2018 at 3:43:43 PM UTC-4, David (Google Cloud 
Support) wrote:
>
> Python 3.7 on App Engine standard provides the GCE metadata service, so as 
> an alternative, you could use Compute Engine Credentials 
> .
>  
> I will inform our documentation team to update this document since it is 
> outdated and it does not include App Engine Standard Second Generation as 
> one of the platforms where you could use these credentials.
>

-- 
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/c6605154-16dd-4feb-8b7e-690b0471caf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Second gen GAE Python 3.7 > Cloud SQL - MySQL

[Eric G]

Thanks for this. The second link is to the flex environment documentation. 
Are you saying that App Engine standard 2nd gen uses the same method of 
connecting to CloudSQL instances as flex, i.e. via the unix socket  
/cloudsql/INSTANCE_CONNECTION_NAME ?  If so, it would be helpful to have 
those instructions/example on the first link (to standard 2nd gen) as well.

Personally, I would like to see an example that doesn't depend on 
SQLAlchemy + Flask, otherwise people may think they have to use those. I 
guess it's not hard to figure out but just some acknowledgement that you 
can set your own environment variables and manually use them to connect 
with pymysql or whatever adapter.


On Tuesday, September 11, 2018 at 11:22:24 PM UTC-4, Olu wrote:
>
> There are different ways to connect to the CloudSQL instance depending on 
> the location from where you are connecting. If you are connecting from an 
> App Engine instance which is located in a project which is different from 
> the project which the CloudSQL instance resides, you must use a service 
> account to allow connection between the App Engine application and the 
> Cloud SQL as described in the link 
> 
> .
>
> However, when connecting from your App Engine Application within the same 
> project, you simply have to configure your app.yaml with the user, 
> password, database, and instance connection name variables from Cloud SQL, 
> See the documentation 
> 
> . 
>
> External applications have to connect to the Cloud SQL instances directly 
> through the public IP address and the IP addresses of the connecting 
> application have to be white listed in the Cloud SQL instance on the 
> Authorization Tab of the Instance page.
>
>
>

-- 
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/ee4e12f4-14f7-4373-863e-65b9ab34435c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Google auth default credentials for GAE standard 2nd Gen (Python)

[Eric G]

It appears that the google-auth default credentials 
 will not 
work for 2nd generation standard environments, at least not for Python at 
the moment, as it requires the app identity/user API.

Is there a plan for getting default app engine credentials to work in 
another way?  Or is the recommendation to set the 
GOOGLE_APPLICATION_CREDENTIALS env var to point to the service account file 
manually?

Thanks,
Eric

-- 
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/ee6eb2c1-567f-4670-aa81-2c5a261727dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Back to GAE after some years

[Eric G]

Re. NDB, there is an open source library very similar to it, Python 3 
compatible:  https://github.com/Bogdanp/anom-py.  I can't say I've used it, 
but I highly respect the author's other libraries. 

It includes transparent caching, though with GAE flex or standard Python3 
you have to run your own memcache service.  
See https://cloud.google.com/appengine/docs/standard/python3/python-differences 


On Wednesday, August 22, 2018 at 9:13:58 AM UTC-4, Roberto Martino wrote:
>
> Hi
> Four years ago, I created a complete application using GAE. This 
> appication is still in use.
> I was very happy with GAE and now, getting back to GAE now, I expect the 
> same experience, but it seems that many things are changed, also the 
> documentation changed a lot.
> I'm interested in using Python 3.x
>
> I'd love if anyone can correct me if I'm wrong and answer my questions.
>
> Database
> - blobstore -> deprecated, not a problem I see the alternative
>
> - datastore -> I enjoyed very much the philosophy behind Datastore and NDB.
> has NDB been substitued by Cloud Datastore Client Libraries or can I 
> still use NDB or is there any other best practice?
>
> Android and iPhone App
>
> Push Notifications
> -I used GCM for Android  Notifications and a custom python library for 
> Apple notifications -> deprecated
>I understand that now I must use Firebase.
>Can I use Firebase only for the Push Notifications and keep using 
> Datastore for the DB?
>
> Mobile  comunication, this is an important point for me.
> -I used Google Cloud Endpoints, very nice, very useful and fast for 
> building mobile devices comunication
>Is this still the best way for mobile comunication?
>I red that it does not works with python 3.x, will it be ported shortly?
>
> Thank you in advance
> Roberto
>
>

-- 
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/c0373c50-ac3f-4273-b30f-0e22c7052318%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: python 3.7 standard runtime release schedule?

[Eric G]

Is there a document that describes the differences between Python 3 
standard and flex?   At a quick glance at least the interface for Python 3 
standard looks very similar to flex.  Thanks.
>
>
>

-- 
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/0a25869c-685d-4260-a56b-4cec4e870fc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: python 3.7 standard runtime release schedule?

[Eric G]

Thanks! That's great news and very helpful links.

-- 
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/21bf190b-ef62-4791-94d6-4f7dae8000f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] python 3.7 standard runtime release schedule?

[Eric G]

Apologies if this has already been asked, but now that python 3.7 standard 
has been announced, what is the timeframe?  Is there an alpha signup yet?

Thanks.
Eric

-- 
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/99d7d2f5-cea4-47c9-af39-c411fc1e4992%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: service account auth to Calendar API stopped working Oct 20

[Eric G]

Thanks. It seems to work now, oddly without even doing 
credentials.create_delegated (but I may be mistaken, I only tested it 
briefly in an offline context. In my GAE application, I've switched it to 
use standard 3-legged OAuth instead of service accounts).

Anyway, if credentials.create_delegated is essential for service accounts 
with DwD, I would propose making it more obvious in the documentation 
. I 
carefully read that page several times and missed it. The way the document 
hierarchy reads, it looks like it is on the same level as "Google App 
Engine", "Google Compute Engine", and "Other". So if you are looking for 
GAE instructions, you may think it doesn't apply to you. I would suggest 
moving that up one level in the hierarchy so you'd have:

1. Create a Credentials object from the service account's credentials and 
the scopes your application needs access to.

2. If you have delegated domain-wide access to the service account and you 
want to impersonate a user account, use thecreate_delegated method of an 
existing ServiceAccountCredentials object. 

3. Use the authorize method of the Credentials object to apply the 
necessary credential headers to all requests made by an httplib2.Http
 instance. 


I would have left this as a comment, but I don't see a way to give 
documentation feedback on that page.

Thanks again,
Eric


On Tuesday, November 1, 2016 at 11:22:12 AM UTC-4, George (Cloud Platform 
Support) wrote:
>
> Hello Eric!
>
> For your new service accounts, your code imports credentials from a stored 
> JSON file, which is one of the possible alternatives, all of which should 
> work well. 
>
> How did you grant domain-wide access to your service account, exactly? 
>
> Did you then implement the OAuth2WebServerFlow as described on the “OAuth 
> 2.0” page 
> ? 
>
>
> If you delegated domain-wide access to your service account successfully, 
> you need to use the "delegated_credentials = credentials.
> *create_delegated*('u...@example.org ')" statement to 
> impersonate a user with the service account, as indicated at the “Delegate 
> domain-wide authority” paragraph on the “Using OAuth 2.0 for Server to 
> Server Applications” page 
> . 
>
> I hope this helps for now. I’ll look at your code and try to reproduce the 
> bug meanwhile, waiting for your reply. 
>

-- 
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/f0336a3b-878d-420a-89fb-0b36511c479a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: service account auth to Calendar API stopped working Oct 20

[Eric G]

Details below. I also opened an issue on the apps-api-issues:
https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=4870=Stars%20Opened%20ID%20Type%20Status%20Summary%20API%20Owner

I successfully switched the app to use 3-legged OAuth vs. service account 
OAuth, but still would like to get to the bottom of this, as I'd prefer to 
use service account OAuth for testing and maintenance programs that hit 
this API, and also for the benefit of others who may be having the problem.

G Suite tech support suggested after setting up DwD you may have to use 
credentials.create_delegated('some.real.u...@example.com')  -- as mentioned 
on this page 
<https://developers.google.com/identity/protocols/OAuth2ServiceAccount> (but 
without any indication that it's necessary, and very easy to miss). I have 
not tried that but will in the next day or two.


On Tuesday, October 25, 2016 at 4:33:25 PM UTC-4, George (Cloud Platform 
Support) wrote:
>
> Hello Eric!
> More detail is needed, to investigate your problem: 
> - About the client library: language, version (GData, API Client ?). 
>

- Python 2.7 App Engine runtime
- google-api-python-client==1.5.3
- oauth2client==4.0.0
 

>  
> - API scopes? 
>
https://www.googleapis.com/auth/calendar 
<https://www.googleapis.com/auth/calendar'> 

- The actual URL posted in your app call. 
>
GET 
https://www.googleapis.com/calendar/v3/calendars/ert.com_2tg0olqm8t766rjutjjc0hns8o%40group.calendar.google.com/events?orderBy=startTime=2016-10-28T00%3A00%3A00Z=nextPageToken%2Citems=true=250=json

POST 
https://www.googleapis.com/calendar/v3/calendars/ert.com_2tg0olqm8t766rjutjjc0hns8o%40group.calendar.google.com/events?alt=json
 

> - Code (HTTP Request)?
>

See issue 
<https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=4870=Stars%20Opened%20ID%20Type%20Status%20Summary%20API%20Owner>
 

>  
> - Are there other accounts affected, or just one, or few? 
>

All the service accounts we set up.
 

> - In case an account works well, email address and user? 
> - Any part of your code you deem significant.  
> - Request output.
>

GET: 

<https://lh3.googleusercontent.com/-r-HOZ91Nh1E/WBTh1yjyYEI/C-0/8u1-gn1JPaMcK_uu4edX-VYM4Dr2zSC9QCLcB/s1600/calendarapiGET.png>


POST:

<https://lh3.googleusercontent.com/-TrhzBL4xx6o/WBTh7qKBFcI/C-4/ecbgPgWSrPIrensRlvRCvk9EubNBcNVygCLcB/s1600/calendarapiPOST.png>


 

>
> - Eventual screenshots of the results, if relevant. 
> - If possible, HTTP Request and Response headers, or full HTTP logs. 
>
> Waiting for information; let me know if I may help otherwise. 
>
> On Monday, October 24, 2016 at 2:46:28 PM UTC-4, Eric G wrote:
>>
>> I have a GAE project (python 2.7 runtime) that uses the Google Calendar 
>> API v3. Up until last week, I had been using the default GAE service 
>> account to connect to the calendar API, and the service account was given 
>> read/write permission to the calendar under calendar sharing settings.
>>
>>
>> Since last Thursday Oct 20, the service account cannot write to the 
>> calendar (events.post or events.patch) -- returns a 403 Forbidden -- and 
>> reads (events.list) return 200, but no records. Checking the permissions 
>> for the account under calendar sharing, it has been changed to "See 
>> Free/Busy only".
>>
>>
>> I believe this is related to this announcement from Google about winding 
>> down OAuth 1.0 service accounts on Oct 20: 
>> https://developers.googleblog.com/2016/04/saying-goodbye-to-oauth-10-2lo.html
>>
>>
>> The recommendation seems to be to grant Domain Wide Delegation to the 
>> service account: 
>> https://developers.google.com/identity/protocols/OAuth2ServiceAccount#delegatingauthority
>>
>>
>> We have followed the instructions on this page, but it doesn't work using 
>> either AppAssertionCredentials or ServiceAccountCredentials.  
>>
>> More details at this SO question:
>>
>> http://stackoverflow.com/questions/40223292/google-app-engine-auth-for-google-apis-using-service-account
>>
>> Thanks for any light you can shine on this problem.
>>
>>
>>
>>

-- 
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/58b79a43-1b53-4407-9916-01961f31537b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] service account auth to Calendar API stopped working Oct 20

[Eric G]

I have a GAE project (python 2.7 runtime) that uses the Google Calendar API 
v3. Up until last week, I had been using the default GAE service account to 
connect to the calendar API, and the service account was given read/write 
permission to the calendar under calendar sharing settings.


Since last Thursday Oct 20, the service account cannot write to the 
calendar (events.post or events.patch) -- returns a 403 Forbidden -- and 
reads (events.list) return 200, but no records. Checking the permissions 
for the account under calendar sharing, it has been changed to "See 
Free/Busy only".


I believe this is related to this announcement from Google about winding 
down OAuth 1.0 service accounts on Oct 20: 
https://developers.googleblog.com/2016/04/saying-goodbye-to-oauth-10-2lo.html


The recommendation seems to be to grant Domain Wide Delegation to the 
service account: 
https://developers.google.com/identity/protocols/OAuth2ServiceAccount#delegatingauthority


We have followed the instructions on this page, but it doesn't work using 
either AppAssertionCredentials or ServiceAccountCredentials.  

More details at this SO question:
http://stackoverflow.com/questions/40223292/google-app-engine-auth-for-google-apis-using-service-account

Thanks for any light you can shine on this problem.



-- 
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/85d501e3-6cbd-4616-95cc-39392acc75b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Task Queue: googleapi: Error 500: Backend Error

[Eric G]

Hey, thanks for this Frank(s)!  Solved my problem too. I'm submitting a 
feedback request to Google's documentation on this.

One other thing I had to do was make sure my project in the URL was 
prefixed with s~, as suggested in responses to the SO question here:
http://stackoverflow.com/questions/20052778/google-app-engine-task-queue-googleapi-error-500-backend-error?rq=1

Eric

On Tuesday, August 26, 2014 at 8:47:50 PM UTC-4, Frank Ren wrote:

 Hi

 Did you solve your problem?

 I got the same problem... Just solved it by supplying to request body a 
 property, queueName, which is not documented.

 Frank, yet another :)

 On Tuesday, November 19, 2013 12:49:00 AM UTC+8, Frank Blechschmidt wrote:

 Hey :)

 I've defined a pull queue for my app engine application and want to fill 
 it from outside via the REST api. Unfortunately it doesn't work, I always 
 get an error 500: backend error. Even if I try to fill it with the api 
 explorer from thedocumentation.

 https://developers.google.com/appengine/docs/go/taskqueue/rest/tasks/insert

 It responses:

 500 Internal Server Error
 - Show headers -
 {
  error: {
   errors: [
{
 domain: global,
 reason: backendError,
 message: Backend Error
}
   ],
   code: 500,
   message: Backend Error
  }}

 Any idea how to solve it?

 Best regards Frank



-- 
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d0ef1c70-51be-4ee9-ab98-4d67e9775deb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.