When client is configured using url, port seems to be incorrectly set on some methods
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 464
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
I have a weird error: when Qdrant client is initialized with a full URL (ie https://hostname:port), client methods fails with a fetch failed / timeout errors but some don't.
The code:
const qdrantClient = new QdrantClient({ url: 'https://mydomain.com:443' });
try {
await qdrantClient.getCollection('test');
} catch (e) {
console.log(e);
}
When used locally with a URL like http://localhost:6333 there's no issue, but when the URL is https://mydomain.com:443 I get a fetch failed error.
If I add the port manually in the client setup:
const qdrantClient = new QdrantClient({ url: 'https://mydomain.com:443', port: 443 });
It works normally.
EDIT: It also seems only some methods are affected by this, as I can make search queries just fine without having the port explicitly set?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at QdrantClient initialization and the getCollection entry point; compare how a port supplied in the URL is handled with a manually supplied port. Reproduce the HTTPS case using the example, then verify that affected methods work without duplicating the port configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100