Use passed URL as schemasURL when is has /schemas suffix

[raphink]

The X-API-Schemas headers returned by /v1-catalog and child nodes is always /v1, so it's not possible to access the schemas.

With this patch, the API uses the API URL as the schemas URL if it ends with /schemas.

Granted, this should be fixed in Rancher server instead, but at least this PR makes the catalog API usable without upgrading production servers (unless I'm missing something in the docs).

[raphink]

@vincent99 as mentioned on IRC

[ibuildthecloud]

@raphink Is this an issue in Rancher 1.1? There was a problem in which the internal proxy in Rancher would concatenate headers and not replace them. The result was that instead of setting X-API-Schemas to the correct /v1-catalog URL it would return two headers with /v1 first. Clients would see only that. The end result is I believe this is fixed already in the Rancher 1.2 releases.

[raphink]

@ibuildthecloud has this been fixed in the server API?

[cjellick]

Very stale. Closing. Thanks! Please open a new PR if there is still a relevant change.