Background:

As part of the deprecation of the CORS proxy, a procedure was provided to prepare SaaS instances for the change.

The provided procedure indicates that if upgrading the Swagger UI is not possible, the following should be added to the script block: 

delete window.swaggerUi.options.transport; 

Issue:

This line does not disable the CORS proxy when Swagger UI 1.2 is used.

Actions Taken:

The following declaration was tested and found to disable the CORS proxy when using Swagger UI 1.2:

window.enableApiDocsProxy = false; 

Request:

• Is the above declaration the correct method for disabling the CORS proxy when using Swagger UI 1.2?