500 codes
This is an open discussion with 3 replies, filed under General.
Search
Perhaps the bug tracker, but this is a good a place as any to raise the idea :)
I agree — a 500 on error would be the sensible thing.
Absolutely right, and I should have done this from the start.
http://github.com/symphony/symphony-2/commit/ce3a03e483e027e1928b186c3323899f9e1897a8
Create an account or sign in to comment.
Not sure if this is the place to post this, but does the latest version of s2 respond with a 500 code if there is a transformation error? This could be handy, and I don't really see a reason not to...
Also, if there is a better place to post things like this, could someone point me that direction?