Turns out, happily, that our vendor has an alternate technique based on POST.
So this can be ignored. Took me a while to figure out what was going on; a logging.warning sure would have helped... j On Wednesday, 27 November 2013 14:55:14 UTC-6, Jason Collins wrote: > > When attempting to perform a urlfetch DELETE call, it seems the payload is > explicitly NOT added. From urlfetch.py: > > if payload and method in (POST, PUT, PATCH): > request.set_payload(payload) > > This makes it impossible to work with an API provided by our vendor. > > Is there any particular reason that a payload cannot be added to a DELETE > urlfetch? > > j > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
