Bug #42565
Updated by Ernesto Puerta over 4 years ago
After Debug mode PR was added, now when an exception is triggered, the error responses from the back-end include a UUID of the request (in order to better match HTTP responses and log traces). In older versions of Cherrypy (like the ones most distros come with), this UUID is not yet implemented, so Debug mode had to provide a work-around for this. That's why there are 2 different implementations for the UUID: the work-around one works, while the native one doesn't. It triggers another exception because of an error when JSON serializing the response. !{width:800px}uuid.png! !{width:400px}uuid.png! In order to avoid different code paths for older-newer versions, I'll basically include the same implementation for both.