An invalid fstab.yaml causes a 500, should be a 502 about helix-content-proxy HOT 5 CLOSED

Probably not a 400, as the issue is not the request per se, but the server config, so maybe a 502

from helix-content-proxy.

https://github.com/adobe/helix-shared/blob/e185e0c079602793f3e665bb41da923f52dc4efc/packages/helix-shared-config/src/ConfigValidator.js#L43-L66

Has an example of getting more nicely formatted error messages, so it is definitely possible to add more context there.

from helix-content-proxy.

In order to detect these kind of errors, I'm wondering whether SchemaDerivedConfig in helix-shared might throw an error that is better detectable than now:

  throw new Error(ajv.errorsText());

May be a specific error type (e.g. ValidationError) or add some extra property (e.g. code)?

from helix-content-proxy.

A 502 would still wake you up in the middle of the night if someone created a new helix project with a malformed fstab (and desperately trying to load the page).

from helix-content-proxy.

🎉 This issue has been resolved in version 2.18.47 🎉

The release is available on:

• v2.18.47
• GitHub release

Your semantic-release bot 📦🚀

from helix-content-proxy.