You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@predictionio.apache.org by mars <gi...@git.apache.org> on 2016/08/05 18:04:05 UTC

[GitHub] incubator-predictionio issue #266: Make TLS/https optional

GitHub user mars opened an issue:

    https://github.com/apache/incubator-predictionio/issues/266

    Make TLS/https optional

    As mentioned in the post-close comments of [this TLS error issue](https://github.com/apache/incubator-predictionio/issues/221#issuecomment-217486391), providing optional plain HTTP would allow `pio deploy` to be supported on proxied/routed app platforms like [Heroku](https://www.heroku.com).
    
    I've been working on a [PIO buildpack for Heroku](https://github.com/mars/prediction.io-buildpack) using the current PredictionIO-0.9.6 release. Once the engine deploys & starts successfully, the Heroku router cannot negotiate a HTTP connection with the PIO engine.
    
    Plain HTTP would also allow generic authentication proxies for the wide-open service provided by `pio deploy`.

----

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-predictionio issue #266: Make TLS/https optional

Posted by dszeto <gi...@git.apache.org>.
Github user dszeto commented on the issue:

    https://github.com/apache/incubator-predictionio/issues/266
  
    Please bring this to user@predictionio.incubator.apache.org (http://predictionio.incubator.apache.org/support/). GitHub issues is no longer supported after ASF migration and will eventually shutdown. Thanks!


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---