Orders not going through on C2 API today

Any known issues happening today? I have multiple servers posting trades that are being recording in my database, but when sent to C2 they seem to be returning the C2 homepage’s HTML.

Hi Terry:

We recently forced all traffic onto https for higher security, but in hindsight that was a bad decision because it “broke” many C2-compatible software programs. We are working on reverting to old settings, but this has proven a bit more complicated than originally expected. For now, if you are able to do so, please just use https (i.e. secure server) when accessing C2 and you should be fine.

I am very sorry about this.

Matthew

Ah, okay… I’ll update now. Thanks.

Why, for heavens sake, couldn’t you enable both protocols in parallel for some time, inform all consumers of these protocols and wait until everybode has acknowledged the change?

This sudden change caused one day without signals (the first in 7 years) and probably quite some angry subscribers.

You are right. I posted an apology about this earlier today on another thread. Let me re-post it here as well:

Yesterday we had a series of problems caused by the fact that we upgraded the entire C2 site security level to use https everywhere. A great idea in theory, but it was actually stupid because I failed to realize doing this would break old third-party software interfaces like NinjaTrader, TradeBullet, home-brewed C2-compatible software, etc. - which were programmed to use plain http, and did not respect our redirect-to-https directives.

After I saw the pitchforks and torches outside our office windows, we quickly re-jiggered our servers to allow old-style http from C2-compatible software.

I really apologize. This was a bone-headed move, and I know it caused a lot of grief. It was a pretty stressful day here in C2 Corporate Headquarters, too, as we wrestled with the server reconfiguration on-the-fly, during the trading day.

The good news is: The site now uses https everywhere where humans tread, but allows http for software clients.

We’ll be more thoughtful about these sorts of things in the future. Again, I’m sorry.

Matthew