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

Always enfore strict header checking [broken] #174

Closed
wants to merge 11 commits into from
Closed

Always enfore strict header checking [broken] #174

wants to merge 11 commits into from

Conversation

tejashah88
Copy link
Member

Updated alexa-verifier-middleware to 0.2.1 from 0.1.9, which removes the strictHeaderCheck option. Either the verification should be completely on, or completely off.

@dblock
Copy link
Collaborator

dblock commented Feb 13, 2017

This forces all kinds of upgrades on people, like bluebird, alexa-utterances, etc., while the library is perfectly compatible with older verisons. I think you should revert package.json and only do the upgrade that is required by the interface change.

@dblock
Copy link
Collaborator

dblock commented Feb 13, 2017

Also build seems to have broken because of the danger upgrade.

@dblock
Copy link
Collaborator

dblock commented Feb 13, 2017

Still broken, revert package.json and do only the update of the minimum version of alexa-verifier-middleware.

@@ -183,15 +183,6 @@ describe("Alexa", function() {
});
});

it("requires a cert header", function() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reason for removing this test?

@tejashah88 tejashah88 changed the title Always enfore strict header checking Always enfore strict header checking [broken] Feb 13, 2017
@tejashah88 tejashah88 closed this Feb 13, 2017
@tejashah88
Copy link
Member Author

@dblock New PR: #178

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

Successfully merging this pull request may close these issues.

4 participants