fix: Parse.Hooks requests have double forward slash in URL

[dplewis]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

Closes: #2406

Approach

Remove extra slash

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, code comments)

[parse-github-assistant]

Thanks for opening this pull request!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (52ddaee) to head (b8213fc).
Report is 3 commits behind head on alpha.

Additional details and impacted files

@@            Coverage Diff            @@
##             alpha     #2441   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           64        64           
  Lines         6256      6256           
  Branches      1476      1476           
=========================================
  Hits          6256      6256           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mtrezza]

Could this possibly be a breaking change, thinking about custom parsing of the URI on the server or firewall?

[dplewis]

@pocketcolin

[mtrezza]

We might want to merge this as a breaking change, make a stable release and then add that to the Parse Sever 8 release as a breaking change. Even though these are internal requests and therefore may be less likely to be restricted by a firewall, it's still possible.

[mtrezza]

BREAKING CHANGE: Internal REST requests for Parse.Hooks use a URL that contains a double forward slash, for example http://localhost/parse//hooks/functions. This release changes the double forward slash to a single forward slash.

@dplewis Is this correct?

[dplewis]

LGTM!

[parseplatformorg]

🎉 This change has been released in version 6.0.0-alpha.2