OAuth issue in Google AppEngine developing?

For POST requests you must pass the oauth parameter url-encoded in the request body. The relavant code in the SDK is this (dev_appserver_oauth. Py).

For POST requests you must pass the oauth parameter url-encoded in the request body. The relavant code in the SDK is this (dev_appserver_oauth. Py): def _Parse(self, request, base_env_dict): """Parses a request into convenient pieces.

Args: request: AppServerRequest. Base_env_dict: Dictionary of CGI environment parameters. Returns: A tuple (method, path, headers, parameters) of the HTTP method, the path (minus query string), an instance of mimetools.

Message with headers from the request, and a dictionary of parameter lists from the body or query string (in the form of {key :value1, value2}). """ method = base_env_dict'REQUEST_METHOD' path, query = dev_appserver. SplitURL(request.

Relative_url) parameters = {} if method == 'POST': form = cgi. FieldStorage(fp=request. Infile, headers=request.

Headers, environ=base_env_dict) for key in form: if key not in parameters: parameterskey = for value in form. Getlist(key): parameterskey. Append(value) elif method == 'GET': parameters = cgi.

Parse_qs(query) return method, path, request. Headers, parameters See that the query is only parsed in GET requests. For POST, it must be in the body.

May be I have found some clue, every time I send a post request with a application/x-www-form-urlencoded Content type, app engine reject me and complains auth failure. ... – itemon May 11 at 2:10.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.