Skip to content

Web support for domain sub-paths #60

@jonpas

Description

@jonpas

Sub-path being eg. example.com/aar

Using ocap-web with Traefik reverse proxy only works with a root domain or a sub-domain. Trying to use a sub-path (with proxy stripping the /aar prefix so it is even accessible) results in the ocap-web's API calls going to the root domain and as expected hitting a 404.

A config entry for setting the root URL where ocap-web should expect assets/API endpoint to be would solve this issue.

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions