HTTPS Parse Error about kappa

[drkibitz]

The error:

{ [Error: Parse Error] bytesParsed: 0, code: 'HPE_INVALID_METHOD' }

[drkibitz]

I think this is probably with the version of hapi. I did try a simple update and the latest hapi version is incompatible with kappa.

[drkibitz]

Turns out is was because of mis-documentation. These say "tls" is a sibling of "options", https://github.com/krakenjs/kappa/blob/master/example/local/config.json#L10-L15
https://github.com/krakenjs/kappa/blob/master/example/global/config.json#L11-L16

When in fact it, "tls" should be a member of "options".

{
    "host": "localhost",
    "port": "env:SSL_PORT|d",
    "options": {
        "tls": {
            "requestCert": true,
            "rejectUnauthorized": true,
            "key": "file:../key.pem",
            "cert": "file:../cert.pem"
        },
        "payload": { "maxBytes": 10000000 }
    }
}

[drkibitz]

I also tested locally editing kappa to get it compatible with hapi 5.0. Turns out the only things that needed changed was references to undefined functions in hapi.utils. These should now be called directly on "hoek". Made those changes, and worked with hapi 5.0.

[totherik]

thanks for digging into this @drkibitz. so is this problem due to changes between versions of hapi or incorrect docs in kappa? if the latter, would it be helpful to call out the different configs by version?

[drkibitz]

@totherik Incorrect docs in kappa. I was just mentioning how easy it was to up hapi to latest.

[drkibitz]

It was my understanding that the config object is dictated by node's http module, not hapi. I could be mistaken.

[totherik]

Ahh gotcha, so the examples are just missing an options property/object between server and tls. That's easy enough to correct.

[jasisk]

Closed by #61