Note that there are some explanatory texts on larger screens.

plurals
  1. POSend Message Over Port 80 Using Azure Service Bus
    primarykey
    data
    text
    <p>It seems like the solution to my problem should be easier than it is, which makes me think I'm missing the obvious. I'm trying to test and ensure that a remote client machine can send/receive messages from an Azure Service Bus Queue.</p> <p>I'm using the sample application provided by Microsoft at <a href="https://www.windowsazure.com/en-us/develop/net/how-to-guides/service-bus-amqp/" rel="nofollow">https://www.windowsazure.com/en-us/develop/net/how-to-guides/service-bus-amqp/</a></p> <p>The sample application works perfectly fine as long as all ports are open. However, I need the solution to work when only ports 80/443 are available. If I configure Windows Firewall to only allow inbound/outbound traffic on 80/443 it doesn't work. I receive the error "An attempt was made to access a socket in a way forbidden by its access permissions".</p> <p>The offending line from the sample application is:</p> <pre><code>sender = factory.CreateMessageSender(entityName); </code></pre> <p>I've looked at an extraordinary number of sites and one of the suggestions I've found was to set the connectivity mode to Http such as this:</p> <pre><code>ServiceBusEnvironment.SystemConnectivity.Mode = ConnectivityMode.Http; </code></pre> <p>That doesn't work either.</p> <p>I'm not trying to setup custom services on either the remote client or Azure hosted roles. I just need them to both be able to send/receive messages via Azure's Service Bus Queues and Topics.</p> <p>Can anyone point out my flaw?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload