Treatment of trailing forward slash on Server Object "url".

[charjr]

If you had something like this:

# rest of api...
servers:
  - url: http://petstore.swagger.io/
paths:
  /pets:
    get:
# rest of api...

Assuming no other servers are specified at any level; what would the expected url be for a get request to /pets?

https://petstore.swagger.io/pets
or
https://petstore.swagger.io//pets

[handrews]

The specification requires that the URL template be appended (bolded in the spec), so the result would be https://petstore.swagger.io//pets. Of course, a tool can then choose to normalize URLs in accordance with RFC 3986, but that's outside of the scope of the OpenAPI Specification. Many web servers are configured to normalize such URLs internally (e.g. https://github.com/OAI//OpenAPI-Specification/discussions/3512 brings up this discussion, but still shows the // between OAI and OpenAPI-Specification in the address bar for me).

[charjr]

Thank you for the answering my question so thoroughly and with an easy to follow example.
Also thank you for pointing me at the relevant RFC for further reading.

As you stated, that link also points me back to this discussion, even if I add 10 forward slashes!

[charjr]

Closing this discussion as it has been answered.