chrislongo/HttpShell — Issue #1: Headers not working for Twitter authorization headers
Author: chrislongo
Created: 2011-12-16 03:57:07+00:00
State: open

```
$ httpsh https://api.twitter.com/1/statuses/mentions.json
api.twitter.com:/1/statuses/mentions.json> headers Authorization: OAuth oauth_consumer_key="xxxxxxxxxxxxxxxxxxxxxx", oauth_nonce="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", oauth_signature="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1324007412", oauth_token="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", oauth_version="1.0"
api.twitter.com:/1/statuses/mentions.json> head
Connecting to https://api.twitter.com/1/statuses/mentions.json

HTTP/1.1 401 Unauthorized
status: 401 Unauthorized
>content-length: 87
>set-cookie: ...
>expires: Fri, 16 Dec 2011 03:58:25 GMT
>vary: Accept-Encoding
>server: tfe
>x-runtime: 0.01079
>cache-control: no-cache, max-age=300
>date: Fri, 16 Dec 2011 03:53:25 GMT
>content-type: application/json; charset=utf-8
>www-authenticate: OAuth realm="https://api.twitter.com"
```