[
https://issues.apache.org/jira/browse/AXIS2C-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1383.
-------------------------------------
Fix Version/s: 2.0.0
Resolution: Duplicate
See AXIS2C-1484
> Ability to select the interface(s) that the axis2_http_server listens at for
> http requests
> ------------------------------------------------------------------------------------------
>
> Key: AXIS2C-1383
> URL: https://issues.apache.org/jira/browse/AXIS2C-1383
> Project: Axis2-C
> Issue Type: New Feature
> Components: transport/http
> Reporter: Patrick Cosmo
> Priority: Major
> Fix For: 2.0.0
>
>
> When a server has multiple network interface cards (and therefore multiple IP
> addresses), it is often important to be able to configure which interface a
> service listens at.
> For example, consider a server that has an interface with a public IP address
> and a second interface with a private IP address. If the service is internal,
> you may wish it to be accessible from the private IP address but not the
> public IP address.
> In my particular case, I'm using Axis2/C to build a service that supports a
> WSDL/SOAP API. More specifically, I'm using the same code used to build the
> Axis2/C "axis2_http_server.exe", but I'm embedding this code in my own
> application. For all intents and purposes this is just the
> "axis2_http_server.exe" server being run from inside another application.
> So, even though the "axis2_http_server" may not support a command line switch
> that allows the interface to be configured, even if there was a programmatic
> way to configure this that would meet my requirements, and presumably that of
> others?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
