Deploying Jackson behind a Reverse Proxy

[jamshally]

We would like to deploy Jackson as a stand alone service, under a subdirectory (using a reverse proxy). As far as I can tell from NextJs documentation, support for this can be configured via the basePath variable... but this must be done at build time (not runtime). So, I think this precludes us from using the Docker Image.

Do you know a way around this, or is building Jackson from source the only option here?

Thanks for any input

[deepakprabhakara]

@jamshally Aah interesting use case, we have never tried this before and unfortunately given nextjs can only do this at build time I can't think of any other way to do this other than build from source by using our Dockerfile. I also suspect a few other issues might show up (we might have assumed base path is '' in some places).

[jamshally]

OK, thanks for the reply. I'll post back if I gain any insights from progressing this.

For context, this technique is useful when dealing with organizations with tight network security, where domains (and sub-domains) need allow-listing. One domain to allow-list, it turns out, is much easier than multiple.

[deepakprabhakara]

Thanks @jamshally, that is very good insight.