However, within Login.tsx it seems like /api/1/login is being used instead of api/1/login, which breaks my "context path" thing.
Would it be possible to always use "relative" paths, so evebox can properly hosted within its own context path?
Yes, makes sense. Just an oversight/typo. The reverse proxy I usually test against (SELKS) handles authentication in the proxy, so doesn't use EveBox's login. Should be a simple fix.
I'm trying to run evebox behind a reverse proxy, so I can have an URL towards evebox like: https://something.com/evebox/ See also: https://github.com/jasonish/evebox/wiki/Apache-Reverse-Proxy-Configuration
However, within
Login.tsx
it seems like/api/1/login
is being used instead ofapi/1/login
, which breaks my "context path" thing. Would it be possible to always use "relative" paths, so evebox can properly hosted within its own context path?