Go webserver terminates when receiving "malformed" requests

[anhtbnlpq9]

Hello,

I am running opengist inside a container. The container is alive as long the Go webserver is alive.
I have noticed my container stopping because the webserver has quit.
It seems that some malformed HTTP headers (or HTTP headers with missing information) would make the webserver to terminate, cf. the log I have:

Nov 15 18:58:28 my.host docker[737940]: Opengist
Nov 15 18:58:28 my.host docker[737940]: Using YAML config file: /home/opengist/config/config.yml
Nov 15 18:58:28 my.host docker[737940]: No environment variables config specified.
Nov 26 16:40:57 my.host docker[737940]: 16:40:57 FTL internal/web/server.go:228 error="code=400, message=missing csrf token in request header"
Nov 26 16:40:59 my.host systemd[1]: opengists.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 16:40:59 my.host systemd[1]: opengists.service: Failed with result 'exit-code'.

I have not tried to reproduce the behaviour yet, and wasn't able to catch the HTTP request that made the webserver to terminate.

Thanks.

[realJoshByrnes]

Nov 26 16:40:57 my.host docker[737940]: 16:40:57 FTL internal/web/server.go:228 error="code=400, message=missing csrf token in request header"

This just means the Cross Site Request Forgery token is missing. You could try and do a HTTP POST without the token and see if it crashed.