Http 500 error when navigating to Swagger UI about imposter HOT 6 CLOSED

Hi @sameer-coder, thank you for reporting this.

There is improved handling of regex routes in Lambda in v3.31.1. Please could you let us know if this resolves the issue?

from imposter.

Hello,

Thanks for the update. I no longer get a 500 error but now I am facing the same problem mentioned in this open issue

At the moment, Imposter serves the swagger UI at https://domain.com/_spec. But this path is unreachable because of the way routing is setup in API Gateway. The API Gateway only forwards requests to imposter which match a pattern (example- https://domain.com/api/v1)

The endpoints in the OpenAPI spec still work fine because I can specify /api/v1 as the basePath in the imposter config as well as the OpenAPI spec. Imposter handles this perfectly.

Probably we could add an env var to set a basePath for Swagger UI so that the url becomes https://domain.com/<basePath>/_spec

Thanks for the help!

from imposter.

Hi @sameer-coder, there were some further fixes required to static asset handling in Lambda to get this working.

These are released in v3.31.2.

from imposter.

Thanks @outofcoffee

I will deploy again and report back on the issue

from imposter.

Hi @sameer-coder, from v3.32.0 you can set the environment variable IMPOSTER_OPENAPI_SPEC_PATH_PREFIX, to override the default /_spec prefix.

For example:

IMPOSTER_OPENAPI_SPEC_PATH_PREFIX="/api/core-mock/v1/_spec"

...will make the spec UI accessible at http://localhost:8080/api/core-mock/v1/_spec/

from imposter.

Amazing! Thank you 🙏

from imposter.