s3api middleware does not check pipeline config

Bug #1912391 reported by Alistair Coles
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
Fix Committed
Undecided
Alistair Coles

Bug Description

s3api middleware config options imply that the wsgi pipeline will be checked for valid configuration when the s3api middleware loads [1]. This check is not in fact happening, regardless of the value of the auth_pipeline_check option.

[1] https://github.com/openstack/swift/blob/10d9a737d8d6e5fcc70a0be07df89a1fb57b9739/etc/proxy-server.conf-sample#L575-L581

Changed in swift:
assignee: nobody → Alistair Coles (alistair-coles)
status: New → In Progress
Revision history for this message
Alistair Coles (alistair-coles) wrote :

To reproduce, start a proxy-server with a pipeline:

pipeline = s3api proxy-server

and observe that no exception is raised.

Revision history for this message
Alistair Coles (alistair-coles) wrote :
Changed in swift:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/swift 2.27.0

This issue was fixed in the openstack/swift 2.27.0 release.

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.