In the docu limits the usage for the http verb to "Acceptable values include GET, POST, HEAD, PUT, and DELETE."
If you want to connect to an WebDAV server this limitation is a shop stopper. The reason is the protocol buffer interface, there are only the 5 methods available / hard coded. Look into google/appengine/api/urlfetch_service_pb.py, urlfetch_stub.py and urlfetch.py In development server you can expand the list with (for example) OPTIONS = 6 (and find the other places). This works but deployed on app engine the "urlfetch_stub.py" is the urlfetch api from the google infrastructure. The replacement is not available. What are the reasons to not support other , official HTTP verbs ? With OPTIONS you can get the available verbs from the webserver: http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html: OPTIONS For WebDAV-enabled Webserver are more Verbs available: http://www.ietf.org/rfc/rfc2518.txt: PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, UNLOCK Or why you offer PATCH on google api's, abut not from an app engine webapp? http://code.google.com/apis/tasks/v1/performance.html http://tools.ietf.org/html/rfc5789 - PATCH Hoping this post will change the restricted http verb list, Thanx, Christian Harms -- 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.
