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
The htsget-rs server should reject any unknown config options outright when parsing the config. Because the config can be quite complex, it's easy to mistakenly apply a config option that is unknown, where the server accepts the configuration file and just defaults any missing values. This leads to confusion when the server doesn't behave in the way that the user intended.
For example, say TLS is desired on the ticket server, the cert and key options may accidentally not be put under the ticket_server_tls table:
The htsget-rs server should reject any unknown config options outright when parsing the config. Because the config can be quite complex, it's easy to mistakenly apply a config option that is unknown, where the server accepts the configuration file and just defaults any missing values. This leads to confusion when the server doesn't behave in the way that the user intended.
For example, say TLS is desired on the ticket server, the
cert
andkey
options may accidentally not be put under theticket_server_tls
table:This results in a ticket server that performs no TLS, where the intended config would have been:
The text was updated successfully, but these errors were encountered: