ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Hill (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-6292) Python client caches curl flags between requests causing problems
Date Thu, 03 Jul 2014 18:03:33 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-6292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051772#comment-14051772
] 

Greg Hill commented on AMBARI-6292:
-----------------------------------

Weird.  I think I only tested with python 2.7 - wonder if something changed there.  Unfortunately
the pycurl docs aren't super great, so I don't know what else we can try.  Maybe we just should
create a new pycurl object on each request?

> 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)

Mime
View raw message