暴露在互联网上配置WCF Web服务 [英] Expose WCF Web service on the internet configuration

查看:120
本文介绍了暴露在互联网上配置WCF Web服务的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我试图揭露写在WCF Web服务,以开放的互联网,但我无法将其配置为从外部URL被消耗掉。

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.

Web服务在 HTTPS内部托管://ourportal.internaldomain.intra:9011 / FrontEndWS 和行之有效的。我们已经暴露了web服务上 https://www.internetdomain.com.mt/FrontEndWS 然而,当从外部地址访问它,肥皂的网址仍然引荐到内部地址。

The web service is hosted internally at https://ourportal.internaldomain.intra:9011/FrontEndWS and works well. We have exposed the webservice on https://www.internetdomain.com.mt/FrontEndWS however when accessing it from the external address, the soap URLs still referer to the internal address.

我们的设置如下。我们不需要在内部暴露web服务,只有在互联网上所以这应该简化配置。

Our settings are as follows. We do not need to expose the webservice internally, only on the internet so this should simplify configuration.


    
     
       
       
         
       
     
    

<bindings>
 <basicHttpBinding>
   <binding name="LargeMessagingBinding" maxBufferSize="99999900" maxBufferPoolSize="524288000" maxReceivedMessageSize="99999900">
     <readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="99999900" maxBytesPerRead="99999900" maxNameTableCharCount="2147483647" />
     <security>
       <transport clientCredentialType="Basic" />
     </security>
   </binding>
 </basicHttpBinding>
</bindings>
<behaviors>
 <serviceBehaviors>
   <behavior name="ServiceBehaviour">
     <serviceMetadata httpGetEnabled="false" httpsGetEnabled="true"  />
     <serviceDebug includeExceptionDetailInFaults="true" />
     <dataContractSerializer maxItemsInObjectGraph="6553600" />
   </behavior>
 </serviceBehaviors>
</behaviors>
<serviceHostingEnvironment aspNetCompatibilityEnabled="false" multipleSiteBindingsEnabled="false" />

推荐答案

我有同样的问题,现在想通了,这是因为offloader这是盈方的Web服务器的SSL的。请与您的管理员组。我们摆脱了SSL的offloader,我们不得不作出的服务了。
您可以参考下面

I had the same problem and now figured out that it was because of the SSL offloader which was infront of the web server. Check with your admin group. We got rid of SSL offloader as we had to make the service up. You can refer to the links below

<一个href=\"http://blogs.msdn.com/b/distributedservices/archive/2010/06/01/ssl-offloader-using-wcf-4-0-routing-service.aspx\" rel=\"nofollow\">http://blogs.msdn.com/b/distributedservices/archive/2010/06/01/ssl-offloader-using-wcf-4-0-routing-service.aspx

<一个href=\"http://blogs.msdn.com/b/distributedservices/archive/2010/05/13/wcf-and-intermediate-devices.aspx\" rel=\"nofollow\">http://blogs.msdn.com/b/distributedservices/archive/2010/05/13/wcf-and-intermediate-devices.aspx

此外,添加主机头用于HTTPS

Also add host header for https

http://www.sslshopper.com/文章-SSL-主机头,在IIS的7.html

这篇关于暴露在互联网上配置WCF Web服务的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆