You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This actually would invoke the ProxyModule which triggers an error because of a missing upstream configuration (by default, appserver.xml has NO upstream configuration).
To avoid misconfigurations, the CoreModule should check, if the module, a file handler references is available or not. If not, a 500 error should be triggered and a debug message should be written to the error log.
Additional Optimization:
It would make sense, to NOT hardcode module names, but instead make them configurable in appserver.xml like
Actually there is a chance to misconfigure file handlers by specifying the
name
of a not existing module, likeThis actually would invoke the ProxyModule which triggers an error because of a missing upstream configuration (by default,
appserver.xml
has NO upstream configuration).To avoid misconfigurations, the
CoreModule
should check, if the module, a file handler references is available or not. If not, a 500 error should be triggered and a debug message should be written to the error log.Additional Optimization:
It would make sense, to NOT hardcode module names, but instead make them configurable in
appserver.xml
likeThese names can then be used for the file handler configuration later on, without the need to know the modules names from the source code.
The text was updated successfully, but these errors were encountered: