You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by rnewson <gi...@git.apache.org> on 2016/09/27 15:17:53 UTC

[GitHub] couchdb-chttpd pull request #141: Fix SSL defaults

GitHub user rnewson opened a pull request:

    https://github.com/apache/couchdb-chttpd/pull/141

    Fix SSL defaults

    Three properties had their defaults changed to a value that
    couch_util:parse_terms throws up on.
    
    "nil" was changed to undefined in COUCHDB-2561 as part of normalising
    the config API. The change from list to atom was a mistake.
    
    COUCHDB-3162

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

    $ git pull https://github.com/cloudant/couchdb-chttpd 3162-ssl-defaults

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

    https://github.com/apache/couchdb-chttpd/pull/141.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 #141
    
----
commit f1d0c5dc8e9ea8c639d39ff63001f3925d6786e8
Author: Robert Newson <rn...@apache.org>
Date:   2016-09-27T15:15:44Z

    Fix SSL defaults
    
    Three properties had their defaults changed to a value that
    couch_util:parse_terms throws up on.
    
    "nil" was changed to undefined in COUCHDB-2561 as part of normalising
    the config API. The change from list to atom was a mistake.
    
    COUCHDB-3162

----


---
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] couchdb-chttpd issue #141: Fix SSL defaults

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

    https://github.com/apache/couchdb-chttpd/pull/141
  
    Ah makes sense, it would be inconsistent.  It takes external-like things (string and binaries), atoms don't fit there.


---
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] couchdb-chttpd pull request #141: Fix SSL defaults

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/couchdb-chttpd/pull/141


---
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] couchdb-chttpd issue #141: Fix SSL defaults

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

    https://github.com/apache/couchdb-chttpd/pull/141
  
    no, I don't think so.


---
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] couchdb-chttpd issue #141: Fix SSL defaults

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

    https://github.com/apache/couchdb-chttpd/pull/141
  
    +1
    
    couch_util:parse_term has a clause for binaries, should be change it to handle atoms as well?


---
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.
---