Axis、wsdlsoap：地址定位和反向代理

发布于 2024-12-07 07:37:10 字数 805 浏览 2 评论 0原文

我使用 AXIS 1.4 生成一些 Web 服务。

这些 Web 服务将由客户端调用，但它们的调用将通过反向代理（带有 mod_proxy 的 apach）。

该过程工作正常，但是在生成的 wsdl 中（当调用 http://proxy/services/ServiceName?wsdl) axis 生成以下块：

<wsdl:service name="MyService">
      <wsdl:port binding="impl:MyServicePortSoapBinding" name="MyServicePort">
         <wsdlsoap:address location="http://internalserver:8080/myapp/services/ServiceName"/>
      </wsdl:port>
</wsdl:service>

wsdlsoap:address 仍然指向防火墙后面的内部服务器 - 不是反向代理服务器。虽然现阶段这对我的测试客户端来说似乎不是问题，但我对在 wsdl 中公开此类信息（服务器名称等）持谨慎态度。

我尝试在 server-config.wsdd 文件的配置中添加 wsdlFile 标记，指向手动更新的WSDL，没有成功（它一直显示以前的信息）。

原文

I've used AXIS 1.4 to generate some webservices.

These webservices will be called by clients, but their calls will go through a reverse proxy (apach with mod_proxy).

The process is working fine, however in the generated wsdl (when calling http://proxy/services/ServiceName?wsdl) axis generates the following block:

<wsdl:service name="MyService">
      <wsdl:port binding="impl:MyServicePortSoapBinding" name="MyServicePort">
         <wsdlsoap:address location="http://internalserver:8080/myapp/services/ServiceName"/>
      </wsdl:port>
</wsdl:service>

The wsdlsoap:address still points to the internal, behind the firewall server - not the reverse proxy one. Although it does not seem to be a problem for my test clients at this stage, I'm wary of letting such information (servername, etc) public in the wsdl.

I've tried adding a wsdlFile tag in the <service> configuration in the server-config.wsdd file, pointing to a manually updated WSDL, without success (it keeps displaying the previous information).

分享到QQ

分享到微博