Fix default parse server url

[wangmengyan95]

We need to add additional / at the end of our default server URL address. Otherwise, when we use new URL(server, httpPath) to build the URL here, the /1 will be ignored.
cc @richardjrossiii

[facebook-github-bot]

By analyzing the blame information on this pull request, we identified @richardjrossiii, @grantland and @wangmengyan95 to be potential reviewers.

[grantland]

Fixes #352

[grantland]

@richardjrossiii Does this comply with the batch issue raised in #330?

[richardjrossiii]

@grantland Yes, URLs are constructed identically in batch vs normal creation.

[wangmengyan95]

@grantland @richardjrossiii any other opinions about this fix?

[grantland]

As long as everything works, I think it's fine. The original concern with trailing slashes was that it would cause a double slash which would mean root:

https://api.parse.com/1//blah -> https://api.parse.com/blah

Are you sure this scenario won't be an issue?

[wangmengyan95]

@grantland, just tested

URL root = new URL("https://api.parse.com/");
String path = "/123";
URL url = new URL(server, path);

The finial url is https://api.parse.com/123, no double slash.

[grantland]

Awesome, LGTM

[richardjrossiii]

Hey guys, we may want to re-investigate this. I just tested (locally, and here), it definitely converts a double slash into a path for root.

[wangmengyan95]

Yep, I do a more through test here.

[grantland]

Discussed in person. The original concern comes from the fact that the paths in iOS/.NET are defined with a leading /, so passing in a server path with a trailing / will yield // which changes the URL to root. We don't define paths in Android with leading /, so this is not an issue.

[facebook-github-bot]

@wangmengyan95 updated the pull request.