Qdrant API ignores base URL path when server URL contains a subpath

[vterrisse]

Hi,

When configuring the Qdrant server URL without a path, everything works as expected:

• https://my-qdrant ✅
  → The Qdrant API functions correctly.

However, when the server URL includes a subpath:

• https://my-qdrant/path1/path2 ❌
  → The Qdrant API ignores /path1/path2, and requests are sent as if the base path did not exist.

Root cause

This behavior seems to be caused by the use of a leading / in the url argument passed to urljoin.
A leading slash causes urljoin to override the base path entirely, instead of appending to it.

Example from qdrant_client/http/api/points_api.py:

return self.api_client.request(
    type_=m.InlineResponse20016,
    method="POST",
    url="/collections/{collection_name}/points/scroll",
    headers=headers if headers else None,
    path_params=path_params,
    params=query_params,
    content=body,
)

Because the url starts with /, any path defined in the base server URL (e.g. /path1/path2) is discarded.

Proposed change

Remove the leading slash so that the endpoint is correctly appended to the base URL:

return self.api_client.request(
    type_=m.InlineResponse20016,
    method="POST",
    url="collections/{collection_name}/points/scroll",
    headers=headers if headers else None,
    path_params=path_params,
    params=query_params,
    content=body,
)

This change would allow Qdrant to work correctly when deployed behind a reverse proxy or under a subpath.

[uahroberto]

Investigation Report

I took a deep dive into the build pipeline at tools/generate_rest_client.sh to trace the root cause.

Findings:
The client code is autogenerated using the openapi.json fetched directly from the main qdrant/qdrant repository (specifically from docs/redoc/master).

Analysis:
Since the leading slashes in paths (e.g., /collections) originate from the upstream OpenAPI definition, applying a patch here in the Python client generator (e.g., a post-processing sed script) would be brittle and prone to breaking on future generator updates.

Recommended Fix

The issue should be addressed upstream in the Qdrant server repository by updating the OpenAPI definition to remove leading slashes from endpoints.

This approach will:

1. Automatically fix the Python client upon the next regeneration.
2. Fix the issue for other language clients as well.
3. Ensure urljoin works correctly with base paths and reverse proxies without manual patching.

[vedik2002]

I'd like to work on this. The root cause is clear — urljoin discards base paths when endpoint URLs have a leading slash.

Question for maintainers: should the fix go in the generator script (tools/generate_rest_client.sh) as a post-processing step, or should it be addressed upstream in the OpenAPI spec in qdrant/qdrant?

Happy to implement either approach once confirmed.