Trailing slashes in URL leads to a 401 - Propose to normalise #21
Description
When a user leaves a trailing slash in the URL, it seems to lead to a 401 error.
Possibly due to duplicated slashes in the constructed URL. (https://weaviate.slack.com/archives/C017EG2SL3H/p1679441113116839).
While the code examples have been modified in the docs to remove trailing slashes, it might be better UX to allow for both. So I propose to have the client accept both cases.