Handle POST /login when client kicked back to login page

[inada-s]

I've found sometimes when a client failed to connect battle server, goes back to a loginpage and requests POST /login with following parameters.

login_1      | I1008 17:20:23.472593       1 top.go:91] map[connection-id:[111111111] user-id:[XXXXXXX]]

Should handle it.

[gh0stl1ne]

You mean players are kicked back to the web login instead of the lobby?

[inada-s]

You mean players are kicked back to the web login instead of the lobby?

Yes.

I used the path POST /login for the login button in lobby server. It works fine.
When a client failed to connect a battle server, sometimes the client is kicked back to webpage (not lobby) and then, requests POST /login again, but it shows only background image.

I want to handle it but I don't know which response would be better.