[GitHub] zeppelin pull request #1489: ZEPPELIN-1321 Zeppelin HTTP and HTTPS port shou...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/1489


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1489: ZEPPELIN-1321 Zeppelin HTTP and HTTPS port shou...

[r-kamath]

GitHub user r-kamath opened a pull request:

https://github.com/apache/zeppelin/pull/1489

ZEPPELIN-1321 Zeppelin HTTP and HTTPS port should be managed seperately

### What is this PR for?
Use a different variable for ssl port number
- add new property for ssl port

### What type of PR is it?
Improvement

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1321

### How should this be tested?
Add ZEPPELIN_SSL_PORT or  zeppelin.server.ssl.port in zeppelin env or site 
xml and configure the rest of ssl properties and start zeppelin.

### Screenshots (if appropriate)
n/a

### Questions:
* Does the licenses files need update? n/a
* Is there breaking changes for older versions? n/a
* Does this needs documentation? Updated install doc

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/r-kamath/zeppelin ZEPPELIN-1321

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/1489.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1489


commit 41899b15e04b7f9468cb09177d24edd6978057b5
Author: Renjith Kamath 
Date:   2016-10-05T09:15:13Z

ZEPPELIN-1321 Zeppelin HTTP and HTTPS port should be managed seperately

- add new property for ssl port




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---