Databases
StackOverflow2013
Postsdbo
POExpose WCF Web service on the internet configuration
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POExpose WCF Web service on the internet configuration
    text
    copied!<p>I am trying to expose a webservice written in WCF, to the open internet but i am having trouble configuring it to be consumed from the external url.</p> <p>The web service is hosted internally at <a href="https://ourportal.internaldomain.intra:9011/FrontEndWS" rel="nofollow">https://ourportal.internaldomain.intra:9011/FrontEndWS</a> and works well. We have exposed the webservice on <a href="https://www.internetdomain.com.mt/FrontEndWS" rel="nofollow">https://www.internetdomain.com.mt/FrontEndWS</a> however when accessing it from the external address, the soap URLs still referer to the internal address.</p> <p>Our settings are as follows. We do not need to expose the webservice internally, only on the internet so this should simplify configuration.</p> <p> </p> <pre><code>&lt;bindings&gt; &lt;basicHttpBinding&gt; &lt;binding name="LargeMessagingBinding" maxBufferSize="99999900" maxBufferPoolSize="524288000" maxReceivedMessageSize="99999900"&gt; &lt;readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="99999900" maxBytesPerRead="99999900" maxNameTableCharCount="2147483647" /&gt; &lt;security&gt; &lt;transport clientCredentialType="Basic" /&gt; &lt;/security&gt; &lt;/binding&gt; &lt;/basicHttpBinding&gt; &lt;/bindings&gt; &lt;behaviors&gt; &lt;serviceBehaviors&gt; &lt;behavior name="ServiceBehaviour"&gt; &lt;serviceMetadata httpGetEnabled="false" httpsGetEnabled="true" /&gt; &lt;serviceDebug includeExceptionDetailInFaults="true" /&gt; &lt;dataContractSerializer maxItemsInObjectGraph="6553600" /&gt; &lt;/behavior&gt; &lt;/serviceBehaviors&gt; &lt;/behaviors&gt; &lt;serviceHostingEnvironment aspNetCompatibilityEnabled="false" multipleSiteBindingsEnabled="false" /&gt; </code></pre> <p></p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

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