[
https://issues.apache.org/jira/browse/AMBARI-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051770#comment-14051770
]
subin commented on AMBARI-6292:
-------------------------------
# python
Python 2.6.6 (r266:84292, Nov 21 2013, 10:50:32)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pycurl
>>> c = pycurl.Curl()
>>> c.setopt(pycurl.CUSTOMREQUEST, None)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: invalid arguments to setopt
> Python client caches curl flags between requests causing problems
> -----------------------------------------------------------------
>
> Key: AMBARI-6292
> URL: https://issues.apache.org/jira/browse/AMBARI-6292
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.6.0
> Reporter: Greg Hill
> Assignee: subin
> Labels: newbie, patch
> Fix For: 1.6.0, 1.7.0
>
>
> Currently if you use the python client, if you issue a DELETE request
> followed by a GET request, that GET request becomes a DELETE request. You
> can imagine why that's undesirable.
> The problem is that we set the CUSTOMREQUEST field on the DELETE, but we
> don't unset it on the next GET. pycurl sees it still set and assumes we're
> still doing a DELETE.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
