[
https://issues.apache.org/activemq/browse/SM-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40927
]
Matt Pavlovich commented on SM-1169:
------------------------------------
A couple of other use cases:
Support for virtual host by name- Should these be separate services?
http://companyA.com:8080/serviceA/
http://companyB.com:8080/serviceA/
SSL - Should be by IP+port, and allow multiple services on that IP+port combo
Same SSL cert:
https://192.168.1.1:8080/serviceA/
https://192.168.1.1:8080/serviceB/
https://192.168.1.1:8080/serviceC/
Different SSL cert. Different service?
https://192.168.1.1:8192/serviceA/
https://192.168.1.2:8080/serviceA/ (Note: the ".2" ip addr)
And of course support combinations..
Different services?
http://companyA.com:8080/serviceA/
https://192.168.1.1:8080/serviceA/
http://companyB.com:8080/serviceA/
> Provide support for using a JHC client in the http provider endpoint
> --------------------------------------------------------------------
>
> Key: SM-1169
> URL: https://issues.apache.org/activemq/browse/SM-1169
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-http
> Affects Versions: 3.3
> Reporter: Adrian Co
> Assignee: Bruce Snyder
> Fix For: 3.3
>
> Attachments: http-provider.patch
>
>
> Current http client in the new http provider endpoint uses the jetty client,
> which does not support ssl or proxy. Using the new JHC client supports both
> ssl and proxy. Also, creating a client api to plug the nio implementation of
> the jhc might be useful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
