Make the Get Handler for your app translate the get requests to variables that are called via a function that lives in the post handler.
Ideally your Get handler and your Post handler both call your main function, then you can swap between, or do translation if you need to handle encoding or to limit functions of the Get Handler. From: [email protected] [mailto:[email protected]] On Behalf Of Marcel Manz Sent: Sunday, November 06, 2011 12:22 PM To: [email protected] Subject: [google-appengine] Why push tasks using http-post don't support a query string in the worker url? I'm passing a post-payload to my task-workers and noticed that such tasks cannot use a worker url with parameters attached. Why is there such limitation? I would have liked to use a worker like /worker-url/?param=value in combination with a http post, so the payload is sent in the post but some query parameters could be attached for easier referencing in the dashboard's access logs. The logs do show the queue_name and the task_name, but I would like to add my own parameters in the query string. Thanks Marcel -- 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/-/DWQJNzxCk7QJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
