0

I am experimenting with running a GraphDB server behind a proxy and facing a challenge. The GraphDB is installed as a K8 stateful set with the following ingress rule.

Example: http://mygraphdb.com/graphdb-int/* ==> URL rewrite ==> http://cluster-ip:7200/*

Also the "graphdb.external-url" property is set to http://mygraphdb.com/graphdb-int/

Problem: The Workbench works and Workbench API works The RDF4JAPI also works

However, the RDF4J API does not send the proper Location header in the response and the RDF4J library cannot work. The location header does not add the proxy context path.

Expected: Location http://xxx/graphdb-int/repositories/my-graph/transactions/xxxx

Actual: Location http://xxx/repositories/my-graph/transactions/xxxx

This was tested using directly the K8 service to rule out any header manipulation by ingress.

Is there any specific configuration required? Is it possible at all?

Any help will be appreciated!!

  • try setting `graphdb.vhosts=http://mygraphdb.com/graphdb-int/` in addition to `graphdb.external-url` – yasko Feb 15 '23 at 16:49

0 Answers0