[
https://issues.apache.org/jira/browse/GEODE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Baker updated GEODE-381:
--------------------------------
Fix Version/s: (was: 1.0.0-incubating)
1.0.0-alpha1
> Gfsh using https connections does not work in environments with SSL
> termination
> -------------------------------------------------------------------------------
>
> Key: GEODE-381
> URL: https://issues.apache.org/jira/browse/GEODE-381
> Project: Geode
> Issue Type: Bug
> Components: management
> Affects Versions: 1.0.0-incubating
> Reporter: Jens Deppe
> Assignee: Jens Deppe
> Priority: Critical
> Labels: gfsh
> Fix For: 1.0.0-alpha1
>
>
> In Cloud Foundry we have SSL termination, i.e. our transport path looks
> something like this:
> {code}
> gfsh <---- https ----> ELB <---- http ----> Cluster
> {code}
> Where ELB is an Elastic Load Balancer or HAProxy.
> When attempting to connect using a https URL, the following occurs:
> {code}
> gfsh>connect --use-http
> --url=https://gf-plan-1-dashboard-253bff71-a09b-4f1a-49fb-ef6b13c39c34.gf1.pcf-gemfire.com/gemfire/v1
> Successfully connected to: GemFire Manager HTTP service @
> https://gf-plan-1-dashboard-253bff71-a09b-4f1a-49fb-ef6b13c39c34.gf1.pcf-gemfire.com/gemfire/v1
> gfsh>
> No longer connected to GemFire Manager HTTP service @
> https://gf-plan-1-dashboard-253bff71-a09b-4f1a-49fb-ef6b13c39c34.gf1.pcf-gemfire.com/gemfire/v1.
> gfsh>
> Exiting...
> {code}
> The problem is that gfsh retrieves meta-information consisting of an index of
> commands mapped to URL endpoints. Even though an initial https connection is
> made, the URLs returned in the index are http URLs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
