tempest

tempest/tempest/lib/common/http.py is hard coded to follow re-directs

Bug #1616892 reported by Graham Hayes on 2016-08-25

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	tempest	Fix Released	Wishlist	Dr. Jens Harbott

Bug Description

tempest/tempest/lib/common/http.py is hardcoded to follow redirects, making it impossible to test if an endpoint is returning a 30X response.

Tags:

Graham Hayes (grahamhayes) on 2016-08-25

tags:

added: tempest.lib

Revision history for this message

Tim Simmons (timsim) wrote on 2016-08-25:

https://github.com/openstack/tempest/blob/master/tempest/lib/common/http.py#L53

Revision history for this message

Masayuki Igawa (igawa) wrote on 2016-11-17:

I think this is not a bug but it's good to have this feature which is handle a 30X response for better testing.

Changed in tempest:
importance:	Undecided → Wishlist
status:	New → Triaged

chandan kumar (chkumar246) on 2017-07-13

tags:

added: low-hanging-fruit

Momoka Toyota (mmkmmk57) on 2017-09-15

Changed in tempest:
assignee:	nobody → Momoka Toyota (mmkmmk57)

Momoka Toyota (mmkmmk57) on 2017-09-20

Changed in tempest:
assignee:	Momoka Toyota (mmkmmk57) → nobody

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-07-04: Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/580146

Changed in tempest:
assignee:	nobody → Dr. Jens Harbott (j-harbott)
status:	Triaged → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2018-10-12: Fix merged to tempest (master)

Reviewed: https://review.openstack.org/580146
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=3ffa54e446ed2a8bf6758343a3130ae424d3ddc4
Submitter: Zuul
Branch: master

commit 3ffa54e446ed2a8bf6758343a3130ae424d3ddc4
Author: Jens Harbott <email address hidden>
Date: Wed Jul 4 11:59:49 2018 +0000

Allow to create a rest_client not following redirects

    Some tests need to verify that the first response from an API is indeed
    a redirect, this can not be done if the client automatically follows
    redirects. Introduce a parameter that allows consumers to disable the
    default behaviour, so that they can see the 301 response instead.

Change-Id: I366fa8d1971cd7502a1cd985f5ee6ad5e1ecb216
Closes-Bug: 1616892