-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
feat: Add --unsafely-treat-insecure-origin-as-secure flag to disable SSL verification #11324
Conversation
Thanks for opening a PR @TheAifam5; I would love to land this PR for 1.12 that is be to released on Tuesday, would you mind if I push directly to your PR? |
Also there are a lot of unrelated changes across multiple files (looks like clippy warnings), however they are not pointed out by current CI setup, so I will revert them to make this PR a bit slimmer. |
@bartlomieju I don’t see problem with that, go ahead ;) Do I need to add you to my fork ? The changes were due clippy’s warnings so I decided to „fix” them :) I will next time note that to only fix errors - or how should be such cases handled? |
There's no need, as a maintainer I can push to your fork.
What clippy version are you using? When I run |
it may be because of the nightly I have set as default. |
That's probable, I'm running on latest stable and |
@bartlomieju What's your plan? What would you like to change here? I might have some spare time and might help a little :) |
@TheAifam5 for now I just rolled back unrelated changes. I will do the proper review shortly and let you know. There's some stuff that's wrong at the first glance (there shouldn't be any changes in |
shouldnt this also apply for websocket? |
Let me check that :) EDIT: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TheAifam5 this PR looks mostly good to me - I pointed out a few things that I don't understand why they're needed. Once those point are addresses I'll help you out with refactoring the code to not change deno_core
.
That said, there are tens of files that are changed that are not in any way related to this PR. Please revert those changes. (I believe these might be caused by clippy, but since CI on main
branch doesn't complain, these changes should be removed)
Will do it :) |
#11491 should be landed first, it will provide |
@TheAifam5 after landing #11491 I will rebase you PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - nice work @TheAifam5 !
Thank you for finishing my work @bartlomieju and @ry for such kind words. |
This PR corresponds to the issue #1371 which implement additional flag to the cli, tools, core, extensions and runtime allowing a user to define a domain or a list of domains which should be excluded from certificate validation while connecting or performing the HTTPS requests or disable validation completely.
The name
noCheckCertificate
and derives I found somewhere in issues of Deno repository as an proposal for the naming and decided to stick with it.I will be out for few weeks and I can not continue the work on this code, but I will be able to accept PR in my repository and will be open for discussion.
The first commit is an actual feature implementation, the second is only about fixing issues reported by
./tools/format.js
and./tools/lint.js
and some comment changes - all of the issues reported by those tools are fixed, except the one which I am not able to fix right now.Those 3 tests are failing for unknown reason:
Closes #5931
TODOs:
Thanks for hints @bartlomieju :)