AccountsAPINGException has UUID with 33 chars?!

[alexreg]

I'm getting a UUID with 33 chars in some exceptions. This is clearly invalid and goes against the UUID RFC. Perhaps the hyphenation is weird?

Example:

UUID: prdaan-2882a1-04301100-003735a10b

Response JSON:
{"jsonrpc":"2.0","error":{"code":-32099,"message":"AANGX-0010","data":{"AccountAPINGException":{"errorDetai ls":"","errorCode":"NO_SESSION","requestUUID":"prd aan001-06151309-0011b97b0e"},"exceptionname":"AccountAPINGExceptio n"}},"id":1}

[jabe]

I think I'd be more concerned with the NO_SESSION errorCode. Put that right and the rest should follow.

NO_SESSION A session token header ('X-Authentication') has not been provided in the request

[alexreg]

That’s no problem, I’m deliberately missing out the session token to get this error. I’m more concerned about this UUID being malformed.

[jabe]

That’s no problem, I’m deliberately missing out the session token to get this error. I’m more concerned about this UUID being malformed.

Fair do. I can't find where it mentions a format for it, though I did see an example in the PDF with a couple of hyphens in it.

[alexreg]

Yeah. I thought it would be formatted like a standard UUID (like the library I use expects). Anyway, thanks for the reply.