support relative basePath

[fehguy]

It seems like the requirement for absolute base path for apis is very difficult for folks. I propose we still support it, but allow the spec & tooling to support relative paths.

The rule would be as follows:

if url starts with "http" it will be considered absolute. Otherwise, the scheme, host, and protocol will be derived from the location of the Api Declaration which is being served.

Since this is incremental, and still supports the absolute path that the spec requires, I believe it can be amended to the 1.2 spec w/o a revision.

[webron]

I'm not sure we can add it as an amendment to the 1.2 spec as it may break
3rd party tools.

On Wed, May 7, 2014 at 1:41 AM, Tony Tam notifications@github.com wrote:

It seems like the requirement for absolute base path for apis is very
difficult for folks. I propose we still support it, but allow the spec &
tooling to support relative paths.

The rule would be as follows:

if url starts with "http" it will be considered absolute. Otherwise, the
scheme, host, and protocol will be derived from the location of the Api
Declaration which is being served.

Since this is incremental, and still supports the absolute path that the
spec requires, I believe it can be amended to the 1.2 spec w/o a revision.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/52
.

[webron]

In Swagger 2.0, the basePath was split into 3 parts - scheme, host and basePath (this one being the path only). If either scheme or host are not specified, it is assumed that the scheme and host used to serve the specification are the ones used for the API calls as well.