Hi,
Our API-integrated newsletter management app has again gone offline because the response status code has again mysteriously changed. Last week I confirmed with StreamSend that the code had changed on August 20 from "200" to "200 OK", despite no mention on this list or elsewhere. This morning our app has gone offline anew, and I have confirmed this code has again mysteriously changed, this time back to the original "200".
This updated status code is being sent despite the documentation still reading "200 OK":
http://app.streamsend.com/docs/api/index.htmlI can certainly appreciate the desire to update the API, but making unannounced changes is not helpful.
Jason
Here's the snippet from our log, proving the status code change:
date: "Wed, 28 Aug 2013 18:20:10 GMT"
server: "Apache"
etag: "\"2b5bc14062754c98083c4b1325618b95\""
x-ua-compatible: "IE=Edge,chrome=1"
cache-control: "must-revalidate, private, max-age=0"
x-rack-cache: "miss"
x-request-id: "4e267fc23f42def7006a1778a914ff3f"
set-cookie: "_session_id=c8c4d7e5231276974d3d5681180374ef; path=/; HttpOnly"
status: "200"
vary: "Accept-Encoding"
content-length: "260"
connection: "close"
content-type: "application/xml; charset=utf-8"
completed