st should send user-agent

Yes, st should indeed send a User-Agent header. Unfortunately, this is more difficult than it may seem as client.py functions have to all be updated to accept headers, client.py's Connection class needs to except a set of headers to send on every request, and then st has to be updated to always use Connection with the appropriate User-Agent header. It's on the "to do" list.

I've taken a stab at it in lp:~mnot/swift/lp782463

To be addressed:
  - tests (couldn't find test cases for client)
  - swift has the version baked into it; probably
    needs to be handled by the build process.
  - the UA for everything is 'swift/[version]'. Is it
    desireabe for it to be more specific for other
    tools that use common.client?

we need to reconfirm

er... in this context "st" means the "swift" command line client provided with "python-swiftclient" - it used to be called just "st"

[Expired for OpenStack Object Storage (swift) because there has been no activity for 60 days.]