Experience with new YDB Web Server

I'm in the process of upgrading our instance of the web server from an old M Web Server version.

In general I think to code is cleaner and there has been some good changes. There are some minor issues however, which I will list here.

  1. Automatic JSON parsing and serializing, triggered by Content-Type header. This is inconvenient for us because we use our own JSON parser. We have to work around the issue by either avoiding Content-Type: application/json, or by modifying the web server code. Both are inconvenient. I would prefer if this behavior of the web server could be switched off somehow. See MR for my suggestion for an implementation.

  2. Features to change global directory, working directory and environment variable by HTTP headers. We don't want to use these features and I fear that they can become a security problem. I would prefer if these features could be switched off somehow. See MR for my suggestion for an implementation.

  3. Verbose error logging. The output of zshow "*" is multiple pages long. It seems excessive to log that also on lowest log level. Maybe move that printout to level 1 or 2? See MR for my suggestion for an implementation.

Both 1. and 2. makes the web server less suitable for using with a 3rd party application such as ours.

Then there are some minor things:

  1. The format for the error response after crashes has changed, adding a message key. We parsed this response so that messed things up for us.

  2. I'm sure I though about something more but now I seem to have forgotten... I'll edit it in if I remember!

Edited Jan 17, 2025 by Jens Li
Assignee Loading
Time tracking Loading