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

fixes #91: allow secure variant of scheme when only insecure is given #160

Merged
merged 2 commits into from Dec 13, 2016

Conversation

shekyan
Copy link
Collaborator

@shekyan shekyan commented Nov 30, 2016

No description provided.

@michaelficarra
Copy link
Member

Cool! Initial once-over looks good. I'll do a more detailed review soon.

resource.scheme.equalsIgnoreCase(shpOrigin.scheme);
} else {
schemeMatches = this.scheme.equalsIgnoreCase(resource.scheme);
if (resource.isNetworkScheme() && !resource.scheme.equalsIgnoreCase("ftp") && !this.scheme.equalsIgnoreCase("ftp")) {
Copy link
Member

Choose a reason for hiding this comment

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

I can't find the reason for this ftp exception.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

We don't want to match ftp to any other network scheme.

@shekyan shekyan force-pushed the GH-91 branch 3 times, most recently from 4bd7b3e to 02c2f69 Compare December 8, 2016 23:38
@michaelficarra
Copy link
Member

michaelficarra commented Dec 13, 2016

@shekyan LGTM. But you either need to sign the CLA with your personal email address or amend your commit with your work email.

@shekyan
Copy link
Collaborator Author

shekyan commented Dec 13, 2016

@michaelficarra, that's strange. My both email addresses are in CLA for ages.

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.

None yet

2 participants