286
General Discussion / Re: Improved Blockland authentication for PHP (Fixes auth with special characters)
« on: October 16, 2016, 04:32:34 AM »The auth server always replies with Connection: close, so it makes no difference. It was just one of the things I left in on accident while debugging issues, since Blockland doesn't send a keep-alive header whereas PHP sends one by default.Is it needed to have it there, as we probably want to replicate how Blockland sends it to avoid any issues?
Also, what about the user agent? Is that for debugging purposes as well?
Blockland does not url encode in a way that is even remotely standard, only a few characters are encoded. And the master server appears to only decode in the exact same format. This is why I had to write my own encode rules. If this were not the case zapk's function would have worked with special characters, because it uses http_build_query which automatically url encodes the data you input to it.That is indeed interesting. I knew Blockland did their own things, but I wasn't aware of this fact. Thanks for clearing it up.

