Campfire API Where Art Thou?
So I’m not sure what happened at 37Signals:http://www.37signals.com with their Campfire application, but both Courenay’s marshmallow and Brandon’s Tinder seem to be hosed.
When using both of these tools, on pretty much any request, you get a redirect back:
Location: http://subdomain.campfirenow.com/
<html><body>You are being <a href="http://subdomain.campfirenow.com/">redirected</a>.</body></html>
The campfire API was never set in stone, and that agile development requires the breaking of a few eggs. That being said, we’ve got a few products (cough CI cough) which really liked being able to integrate with our campfire rooms.
37Signals, DHH, if you’re listening: Please drop us a hint about the new(?) campfire API.
Much appreciated.
Comments
Commenting on your own post? hmmm….
So I just realized that we had recently upgraded accounts to enable optional ssl support—so this could easily be a result of that. Even so, this still means that campfire and tinder won’t work with ssl-enabled accounts.
You scared me for a minute there. I’ve got a client that is using Tinder in production.
I ran into the same problem when I upgraded to an SSL account. I’m not sure why Campfire cares that you’re not using https. I guess I should fix tinder to account for that an automagically switch to ssl.
If you ever do have an issue with Tinder, please email me.
Leave a comment...