Skip to content

apiPath configuration not respected #195

@krodyrobi

Description

@krodyrobi

In reverse proxy situations

/proxy/swagger/odata/v4/<service> -> /swagger/odata/v4/<service> (cds mountpoint)
With /proxy/(.*) redirecting to /$1

Should produce html with
-> /proxy/odata/v4/<service>/<Entities> (generated urls)
-> /proxy/swagger/odata/v4/<service>/openapi.json

{
  "swagger": {
    "basePath": "/swagger" // express mountpoint exposing /swagger/<service>/openapi.json
    "apiPath": "/proxy"        // should generate outbound links with this prefix
  }
}

I've tried all combinations of prefixes and it either doesn't mount at a path expected by the proxy rewrite, files not found, or links not generated / 301 redirecting to basePaths.

On a quick look the middleware doesn't seem to use options.apiPath for anything, am I missing something?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions