Zend_Json_Server only allows error codes RESERVED for JSON-RPC implementation about zendframework

[zfbot]

This issue was ported from the ZF2 Jira Issue Tracker at
http://framework.zend.com/issues/browse/ZF2-181

Known GitHub users mentioned in the original message or comment:
@adamlundrigan, @ralphschindler

[ralphschindler]

Is this still an issue?

[djskinner]

Actually, I think the current behaviour is correct according to the spec, although it is slightly unclear.

Initially I thought that any integer outside of the reserved range was a value error code. However, looking more closely at the spec (http://www.jsonrpc.org/specification#error_object):

1. "The error codes from and including -32768 to -32000 are reserved for pre-defined errors."
2. -32000 to -32099 Server error Reserved for implementation-defined server-errors.
3. The remainder of the space is available for application defined errors.

If application errors are the same as implementation-defined server-errors then the current behaviour is correct. I guess it depends on your interpretation.

[Loxrie]

I think it's a mistake to close this ticket. There is a related one here (http://framework.zend.com/issues/browse/ZF-11991) that led to this ticket being opened. It contains more discussion. Perhaps it could be re-opened?

[djskinner]

I agree. The spec is a bit unclear and I've changed my mind again since my last comment. The way I now see it is that application-defined error codes can be any integer outside of the range -32768 to -32000. Zend/Json/Server should prevent applications raising errors with codes in the reserved range but still needs to be able to use the reserved codes in its own operation in order to conform with JSON-RPC.

[Loxrie]

That was my interpretation too. The specification is rather fluffy in its use of english.

[rkoe]

I'm one of the main authors of the JSON-RPC 2.0 specification.
The correct interpretation is:

• -32768 to -32000 / pre-defined errors: These error-codes and their meanings are defined by the JSON-RPC 2.0 specification.
• -32099 to -32000 / implementation-defined server-errors: These error-codes can be used for JSON-RPC 2.0 servers/frameworks/libraries for their own errors (e.g. if the JSON-RPC-server itself fails).
• all other codes (>-32000 or <-32768) / application defined errors: These can freely be used by procedures which are called via JSON-RPC.

Hope this helps.
If you have any more questions about JSON-RPC, please mail me or write a mail to the JSON-RPC mailinglist
[email protected].

[djskinner]

Thanks for that clarification rkoe. This issue needs to be re-opened then.

[Loxrie]

Excellent thank you. It'd be good to get this into V2.

On 19 Mar 2013, at 18:31, rkoe [email protected] wrote:

I'm one of the main authors of the JSON-RPC 2.0 specification.
The correct interpretation is:

-32768 to -32000 / pre-defined errors: These error-codes and their meanings are defined by the JSON-RPC 2.0 specification.
-32099 to -32000 / implementation-defined server-errors: These error-codes can be used for JSON-RPC 2.0 servers/frameworks/libraries for their own errors (e.g. if the JSON-RPC-server itself fails).
all other codes (>-32000 or <-32768) / application defined errors: These can freely be used by procedures which are called via JSON-RPC.
Hope this helps.
If you have any more questions about JSON-RPC, please mail me or write a mail to the JSON-RPC mailinglist
[email protected].

—
Reply to this email directly or view it on GitHub.

[Loxrie]

Over a year later and nobody has re-opened this bug?

[Ocramius]

@Loxrie open a PR with a failing test case

[Loxrie]

** And I've just read the source code, it's actually resolved... this becomes painfully obvious when comparing Zend/Json/Server/Error.php between ZF2 and ZF1, where the bug still exists. **