Skip to content
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

Closed
AjkayAlan opened this issue Aug 28, 2018 — with docs.microsoft.com · 9 comments
Closed

Add TransportType=AmqpWebSockets As Example #14133

AjkayAlan opened this issue Aug 28, 2018 — with docs.microsoft.com · 9 comments

Comments

Copy link

AjkayAlan commented Aug 28, 2018

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.

@asergaz
Copy link
Contributor

asergaz commented Aug 29, 2018

Thanks for the valuable feedback @AjkayAlan ! I have assigned the issue to the content author to evaluate and update as appropriate.

@LarsCelie
Copy link

This issue helped as I wanted to do exactly that, but didn't find it in the documentation.

@breyed
Copy link
Contributor

breyed commented Mar 13, 2019

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.

@spelluru
Copy link
Contributor

@axisc - please look into when you get a chance. Thanks.

@PRMerger9 PRMerger9 added the Pri2 label Sep 9, 2019
Copy link

gord888 commented Feb 18, 2020

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.

@coolhome
Copy link
Contributor

coolhome commented Feb 20, 2020

@gord888 Is that transport type actually supported in Microsoft.ServiceBus.Messaging? I know in the new SDK Microsoft.Azure.ServiceBus that this is implemented and documented.

https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.servicebus.transporttype?view=azure-dotnet

@spelluru
Copy link
Contributor

Microsoft.ServiceBus.Messaging doesn't actually support AmqpWebsockets.

It's only supported in Microsoft.Azure.ServiceBus as mentioned above.

@spelluru
Copy link
Contributor

https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-amqp-dotnet#amqp-over-websockets

#please-close

@sijucm
Copy link

sijucm commented Apr 12, 2021

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests