Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Secure Socket parsing fails when additional fields exists in the config #573

Open
xlight05 opened this issue Aug 8, 2022 · 0 comments
Open
Assignees
Labels

Comments

@xlight05
Copy link
Contributor

xlight05 commented Aug 8, 2022

Description:

Consider the following scenario which fails to extract the config map.

listener http:Listener securedEP = new (9090,
    httpVersion = "1.1",
    secureSocket = {
        key: {
            path: "./security/ballerinaKeystore.p12",
            password: "ballerina"
        }
    }
);

However the following code works.

listener http:Listener securedEP = new (9090,
    secureSocket = {
        key: {
            path: "./security/ballerinaKeystore.p12",
            password: "ballerina"
        }
    },
    httpVersion = "1.1"
);

Steps to reproduce:

Affected Versions:

OS, DB, other environment details and versions:

Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant