Can't Load Specs via URL?

[rockmasterflex69]

Q&A (please complete the following information)

• OS: Windows
• Browser: chrome
• Version: Version 116.0.5845.111 (Official Build) (64-bit)
• Method of installation: official docker container
• Swagger-Editor version: swaggerapi/swagger-editor:v4.10.2
• Swagger/OpenAPI version: OpenAPI 3.0

Describe the bug you're encountering

Cannot load specs by URL

I can load external yaml specs through the Swagger Editor UI's load button, but NOT through navigation.

• I can load https://raw.githubusercontent.com/OAI/OpenAPI-Specification/main/examples/v3.0/link-example.yaml through the UI,
• but navigating to http://localhost:8083/?url=https://raw.githubusercontent.com/OAI/OpenAPI-Specification/main/examples/v3.0/link-example.yaml just opens petstore.

Worse:
I cannot load yaml specs by URL that are hosted within the container, neither through the load button on the UI nor through the browser bar (eg http://localhost:8083/?url=http://localhost:8083/docs/my_spec.yaml) just opens pet store. These are valid specs and I can reach them directly within the container (as a file download) by going directly to their url like: http://localhost:8083/docs/my_spec.yaml

Actually ^ that was due to a cors issue. I am now using a custom container with cors more or less open wide and manual import of the localhost urls now works. Navigation with /?url still doesn't work though.

To reproduce...

Here is my docker compose:
I am simply doing docker-compose-up and then using the UI @ http://localhost:8083/

version: '3'
services: 
  swagger-editor:
    image: swaggerapi/swagger-editor:v4.10.2
    ports:
      - 8083:8080
    volumes:
      - ./my_spec_files:/usr/share/nginx/html/docs

Expected behavior

I should be able to load whatever spec I define in the URL... not pet store!
My dockerized swagger editor should behave like the live one: https://editor.swagger.io/?url=https://raw.githubusercontent.com/OAI/OpenAPI-Specification/main/examples/v3.0/link-example.yaml

[rockmasterflex69]

I'll also note: there are no browser error messages, nor container ones. It just simply loads pet shop... as if thats what I asked it to do