-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use an unsecured websocket connection if http:// was specified #450
Conversation
The code currently only supports SSL-secured websocket connections, which means the SDK doesn't support testing self-hosted deployments when running on the self-hosted server itself (i.e. `ws://` connections). This change updates the code to use `ws://` rather than `wss://` when the user specifies `http://` in their `api_url`.
WalkthroughThe recent modifications to the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- deepgram/clients/listen/v1/helpers.py (1 hunks)
Additional comments not posted (1)
deepgram/clients/listen/v1/helpers.py (1)
40-49
: Consider edge cases for URL handling.The logic for determining the WebSocket scheme seems correct. However, consider verifying edge cases such as:
- URLs with mixed case schemes (e.g., "HTTP://example.com").
- URLs with additional path or query components.
- URLs that might already include "ws://" or "wss://".
These considerations ensure robustness across various inputs.
Nice! |
Proposed changes
The code currently only supports SSL-secured websocket connections, which means the SDK doesn't support testing self-hosted deployments when running on the self-hosted server itself (i.e.
ws://
connections).This change updates the code to use
ws://
rather thanwss://
when the user specifieshttp://
in theirapi_url
.Types of changes
What types of changes does your code introduce to the community Python SDK?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
Tested!
Summary by CodeRabbit