Ollama URL normalization (leading to issues like #5007) does not clean trailing `/`

[Naam]

App Version

Latest

API Provider

Anthropic

Model Used

N/A

Roo Code Task Links (Optional)

No response

🔁 Steps to Reproduce

See #5007 for more details, it leads people into a lot of confusion (myself included, until the issue was root-caused).

Does not work, show an issue aboud embedding.

works, no issues, difference is the single /

Trailing / in Ollama API URL are not sanitized and will result in API call failures being hidden by unrelated errors about the model not supporting embedding.

💥 Outcome Summary

Trailing / in the Ollama API URL is not sanitized and will result in API call failures being hidden by unrelated errors about the model not supporting embedding.

📄 Relevant Logs or Errors (Optional)

[roomote]

Hi! I'm here to help out the maintainers and am going to see if I can fix this issue. I'll investigate the URL normalization for Ollama endpoints to ensure trailing slashes are properly handled. This should prevent the confusing errors that occur when users accidentally include a trailing slash in their Ollama API URL configuration.

[roomote]

I've created a pull request to fix this issue: #6081

The fix adds URL normalization to handle trailing slashes in Ollama API URLs. This prevents the double slash issue (e.g., http://localhost:11434//api/embed) that was causing 405 errors and misleading error messages.

The solution:

• Created a url-normalization utility that removes trailing slashes from base URLs
• Updated all Ollama-related code to use this utility
• Added comprehensive tests for the URL normalization

All tests are passing and the CI checks have completed successfully (except for an unrelated CodeQL issue). This should resolve the confusing errors users were experiencing when they accidentally included trailing slashes in their Ollama configuration.