[ https://issues.apache.org/jira/browse/SLIDER-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053010#comment-15053010 ]
Steve Loughran commented on SLIDER-907: --------------------------------------- look @ SLIDER-878 for the gory details. something changed in the depths of the JVM and what was there to handle the http->https 302 couldn't do http->http redirections. Moving to a common codebase fixed that and means that things will be consistent in the future, it just looks like this caused the https to http problem to surface (which I think I've now hidden us from), leaving the related question: what about credentials? We aren't currently registering any keystore or similar. Can we just rely on JVM properties to set this up if people want it? And so document it? > AgentWebPagesIT#testAgentWeb fails on wire encrypted clusters > ------------------------------------------------------------- > > Key: SLIDER-907 > URL: https://issues.apache.org/jira/browse/SLIDER-907 > Project: Slider > Issue Type: Bug > Components: registry, test, Web & REST > Affects Versions: Slider 0.80 > Environment: Test cluster with HTTPS set up at the RM Proxy > Reporter: Steve Loughran > Assignee: Steve Loughran > Fix For: Slider 0.90 > > > When you try to run {{AgentWebPagesIT#testAgentWeb}} against a cluster with > the RM proxy set up for HTTPS, the negotiation fails and hence the test -- This message was sent by Atlassian JIRA (v6.3.4#6332)