Comment 2 for bug 770312

Just realise that it was speking about the swift3 middleware and after configuring it I am still getting a proper 403 a la s3 way:

chmouel@linuxcurl -D - -H 'Authorization: AWS foo:bar' http://devstack.chmouel.com:8080/auth/v1.0/
HTTP/1.1 403 Forbidden
Content-Type: text/xml; charset=UTF-8
Content-Length: 124
Date: Thu, 19 Jan 2012 19:56:32 GMT

<?xml version="1.0" encoding="UTF-8"?>
<Error>
  <Code>AccessDenied</Code>
  <Message>Access denied</Message>
</Error>