Thanks Matt - tcpdump to the rescue!  One good and one bad transaction
are shown below.  "[...]" is stuff I've removed.  As you can see, the
only obvious difference, apart from signature generated, is that I've
chopped the end off the tweet in the good transaction... and that such
chopping-off pretty reliably makes the transaction succeed where the
full tweet fails.  I'm afraid I don't have the base signature strings
at present; I'd have to spend some time working out how oauth-proxy
works and modifying it to output them...  Let me know if I need to do
that.

Good transaction:

---SENT---
POST /1/statuses/update.xml HTTP/1.0
content-length: 103
Authorization: OAuth realm="", status="22 Jul 09:19:24: PROBLEM: some-
router [1.2.3.4] (Some test router) is DOWN: PING CRITICAL - Pack",
oauth_nonce="39099550", oauth_timestamp="1280832392",
oauth_consumer_key="[...]", oauth_signature_method="HMAC-SHA1",
oauth_version="1.0", oauth_token="[...]",
oauth_signature="yplz8tgdTMG1UaTCjmdXWxCONbQ%3D"
pragma: no-cache
connection: close
content-type: application/x-www-form-urlencoded
host: api.twitter.com
accept: */*
user-agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/
0.9.8g zlib/1.2.3.3 libidn/1.8 libssh2/0.18

status=22 Jul 09:19:24: PROBLEM: some-router [1.2.3.4] (Some test
router) is DOWN: PING CRITICAL - Pack
---END (no newline at end)---

---RECEIVED---
HTTP/1.1 200 OK
Date: Tue, 03 Aug 2010 10:46:32 GMT
[...]
---END---

Bad transaction:

---SENT---
POST /1/statuses/update.xml HTTP/1.0
content-length: 117
Authorization: OAuth realm="", status="22 Jul 09:19:24: PROBLEM: some-
router [1.2.3.4] (Some test router) is DOWN: PING CRITICAL - Packet
loss = 100%", oauth_nonce="61983556", oauth_timestamp="1280832381",
oauth_consumer_key="[...]", oauth_signature_method="HMAC-SHA1",
oauth_version="1.0", oauth_token="[...]",
oauth_signature="1UQZftmmiDjrqWB%2Fs%2B89nLpVSSw%3D"
pragma: no-cache
connection: close
content-type: application/x-www-form-urlencoded
host: api.twitter.com
accept: */*
user-agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/
0.9.8g zlib/1.2.3.3 libidn/1.8 libssh2/0.18

status=22 Jul 09:19:24: PROBLEM: some-router [1.2.3.4] (Some test
router) is DOWN: PING CRITICAL - Packet loss = 100%
---END SENT (no terminating newline)---

---RECEIVED---
HTTP/1.1 500 Internal Server Error
Date: Tue, 03 Aug 2010 10:46:21 GMT
Server: hi
Status: 500 Internal Server Error
[...]
    <title>Twitter / Error</title>
[...]
          <h2>Something is technically wrong.</h2>
          <p>Thanks for noticing...we're going to fix it up and have
things back to normal soon.</p>
[...]
---END RECEIVED---

Thanks!

--Charles

Reply via email to