namespace/project_name API requiring uri-encoded / causes unnecessary complications

Created by: davidfraser

The documentation for the API implies that /api/v3/projects/namespace%2fproject_name should be a valid way of referring to the project. However, in our system, a request like this ends up being logged as:

Started GET "/api/v3/projects/root%252Ftest?private_token=...

On the other hand, not uri-encoding the / is not supported. The above problem may well be caused by our web proxy, but illustrates that this is a slightly complicated URI scheme to support. Using another character as the namespace-project_name separator would be simpler to implement without having to worry about URL encoding.