Samuel Merritt 288a9d77c5 Fix handling of bad paths in Swift middleware ...

The path //v1/account does not denote any Swift resource. More
importantly, if you call swift.common.utils.split_path() on it (as the
Swift middleware does), then you get a ValueError.

Since it's a bad path, it doesn't refer to any Swift resource, so
there's no stats to publish, so we can just catch and ignore
ValueError.

Change-Id: I9908beef8478c5407985435c1526a9c72edb1d3a

2013-09-10 18:26:35 -07:00

..

__init__.py

Implement object store metering

2012-11-30 11:07:30 +01:00

test_swift_middleware.py

Fix handling of bad paths in Swift middleware

2013-09-10 18:26:35 -07:00

test_swift.py

Change counter to sample in objectstore tests

2013-08-21 16:07:27 +02:00