Petstore no longer honouring explicit HTTPS scheme, and using HTTP instead?

From @alzadude on April 11, 2017 13:37

A recent change to the Petstore seems to have broken the explicit HTTPS api call behaviour.

Steps to reproduce:

1. Go to http://petstore.swagger.io
2. Enter swagger url for the api, using HTTPS (e.g. for one of our api calls, use https://imin-platform-api.imin.co/v1/swagger.json)
3. Specify scheme HTTPS
4. Enter required api parameters (e.g. for one of our api calls, use GET /v1/search/sessions)
5. Click Execute

Expected: Petstore executes api call using HTTPS as specified.

Actual: Petstore appears to execute api call using HTTP (which for our api, doesn’t work unfortunately), and Swagger then shows TypeError: NetworkError when attempting to fetch resource.

Would someone be able to investigate this issue to determine why making the HTTPS scheme explicit isn’t working, and why HTTP is being used instead?

Thanks 😃

Copied from original issue: swagger-api/swagger-core#2171

[shockey]

Latest master doesn’t exhibit this problem (very likely that #2927 fixed it).

Getting a CORS error with this spec:

Fetch API cannot load https://imin-platform-api.imin.co/v1/search/sessions?lat=111&lng=111&radius=111. Response for preflight has invalid HTTP status code 404.

We’re requesting with https, so this looks fixed.

@alzadude, this will be included in our Friday release. If you see any lingering problems, please reply here and I’ll look into it.

Closing!

[r4mbo7]

Solving it by enabling CORS on the aiohttp server side (using aiohttp_cors)

self.webapp = aiohttp.web.Application()
self.webapp.add_routes(routes)
# Add CORS header for the swagger UI
cors = aiohttp_cors.setup(self.webapp, defaults={
    "*": aiohttp_cors.ResourceOptions(
        allow_credentials=True,
        expose_headers="*",
        allow_headers="*",
    )
})
# Configure CORS on all routes.
for route in list(self.webapp.router.routes()):
    cors.add(route)