Looks like a UI bug. Can you file a ticket with the project?
From: <[email protected]> on behalf of Yuto SASAKI <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Monday, December 4, 2017 at 23:12 To: Swagger <[email protected]> Subject: Relative path in OAuth 2.0 authorizationUrl is allowed in OAS 3? Hi, I've found that the doc says The authorization URL to use for this flow. Can be relative to the API server URL. at https://swagger.io/docs/specification/authentication/oauth2/ , and Swagger Editor does not complaint about the following definition: securitySchemes: petstore_auth: type: oauth2 flows: implicit: authorizationUrl: oauth/dialog scopes: write:pets: modify pets in your account read:pets: read your pets However, it seems that Swagger UI goes to own server not the API server. Is this a UI bug, or a documentation bug? -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Swagger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
