Retain session id for subsequent requests

Bug #1837415 reported by Pascal Hofmann
6
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.

Revision history for this message
Pascal Hofmann (pascalhofmann) wrote :

Session id seems to be sent in response header X-Jenkins-Session

Revision history for this message
Pascal Hofmann (pascalhofmann) wrote :

Please ignore comment #1. I thought the bug was related to changed crumb/session behavior, when in reality it was only related to disable_node/enable_node invalidating the crumb.

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.