-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Add TransportType=AmqpWebSockets As Example #14133
Comments
Thanks for the valuable feedback @AjkayAlan ! I have assigned the issue to the content author to evaluate and update as appropriate. |
This issue helped as I wanted to do exactly that, but didn't find it in the documentation. |
Other pages that describe protocol options should be updated, too, such as Optimize performance. Currently, it's not clear what protocols are supported, what the defaults are, and what the default fallbacks are. |
@axisc - please look into when you get a chance. Thanks. |
The TransportType documentation here: https://docs.microsoft.com/en-us/dotnet/api/microsoft.servicebus.messaging.transporttype?view=azure-dotnet... does not list off the AmqpWebSockets as a valid enum. But it does work. |
@gord888 Is that transport type actually supported in |
Microsoft.ServiceBus.Messaging doesn't actually support AmqpWebsockets. It's only supported in Microsoft.Azure.ServiceBus as mentioned above. |
This is not added to the Javascript/NodeJS side and this caused me to waste 3 days of work and frustration. It was not even clearly mentioned which protocol is used when. #Microsoftiness |
Under the section "Configuration using App.config", it may be helpful to add another example showing that you can also use TransportType=AmqpWebSockets on the end of your connection string if you want to use AMQP over WebSockets. I can't find much doc's stating if this is actually supported, but I verified it works as the default AMQP transport port is blocked in my enterprise but when using this option I am able to successfully write messages to a queue. I also verified its a valid option on the enum (https://docs.microsoft.com/en-us/dotnet/api/microsoft.servicebus.messaging.transporttype?view=azure-dotnet).
Perhaps you could even link to https://docs.microsoft.com/en-us/dotnet/framework/network-programming/proxy-configuration (as I have a proxy I must go through), or provide a more direct example to using system default proxy settings if needed.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: