Retain session id for subsequent requests
Bug #1837415 reported by
Pascal Hofmann
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Python Jenkins |
New
|
Undecided
|
Unassigned |
Bug Description
The crumb gets invalid after a call to disable_node / enabled_node. The new crumb from the response should be taken or the crumb should be unset so a new crumb is obtained for all following requests.
To post a comment you must log in.
Session id seems to be sent in response header X-Jenkins-Session