[Enhancement]: nextLink Relative Path Response Enhancement

[Chr0no591]

What happened?

We are currently grappling with the challenge of receiving a relative nextLink path in the form of http(s)://domain.com/path?queries. To address this, we request the implementation of a feature that allows us to obtain only the relative path with queries, excluding the HTTP(S) protocol and domain, like /path?queries. This feature has been discussed in a related question in the Q&A from April 2023; for more details, refer to:
#1447.

To enhance flexibility, we propose implementing a feature with a toggle and configuration option, enabling developers to specify the format of the nextLink response they wish to receive.

Feature Proposal:

• Toggle and Configuration: Introduce a toggle and configuration option to control the nextLink response format.

Configuration Details:
The configuration can be set in the dab-config.json file:

{
  "nextLinkRelative": true // Set to true for relative path only
  "pattern": "domain/path?queries" // or "https://domain/path?queries" it could be a regex pattern or fix
}

Version

0.5.35

What database are you using?

MS SQL

Code of Conduct

• I agree to follow this project's Code of Conduct

[sijpesteijn]

This feature would be very useful. We are facing the same problem when running dab in a container app exposed through a KONG gateway. I see it has been requested a long time ago, but any information if this will be implemented and when? Thank you.

[mdlprel]

Hello!
Are there any updates regarding this Enhancement?

I'm experiencing similar issues in my application deployed on Kubernetes. DAB seems to use absolute addresses instead of relative ones, and this is causing problems:

• In the definition of nextURL
• In Swagger, which fails to find the correct path to the OpenAPI definition.

Thanks!

[JerryNixon]

#2677