This can be fixed but I need to set this up on CGI using Lighttpd or something instead of using the built-in server.
The only issue with moving to the new handler is the fact the http requests become harder to manage.
When Run(server='paste') the client user-agent can break with raw requests out of a browser for instance with HTTPClient.
So identical code ends up not working cross-platform when you access the matchmaking list from another client like a game server announcing using HTTPClient.
Noticed this works fine from Unity's 4.6 net framework, however when a native C# application has issues.
I think this could be the C# HTTPClient's fault as well for not sending the right headers 'x-formdata' etc
it's using a multipartformdata which is interpreted differently depending upon the platform.
This can be fixed but I need to set this up on CGI using Lighttpd or something instead of using the built-in server.
The only issue with moving to the new handler is the fact the http requests become harder to manage.
When Run(server='paste') the client user-agent can break with raw requests out of a browser for instance with HTTPClient.
So identical code ends up not working cross-platform when you access the matchmaking list from another client like a game server announcing using HTTPClient.
Noticed this works fine from Unity's 4.6 net framework, however when a native C# application has issues.
I think this could be the C# HTTPClient's fault as well for not sending the right headers 'x-formdata' etc it's using a multipartformdata which is interpreted differently depending upon the platform.