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.

Sign up for GitHub

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

Jump to bottom

Support self-signed certificates via an option (e.g. -k like in curl) #31

Open
rhuss opened this issue Jun 15, 2021 · 10 comments
Open

Support self-signed certificates via an option (e.g. -k like in curl) #31

rhuss opened this issue Jun 15, 2021 · 10 comments
Labels
triage/accepted Issues which should be fixed (post-triage)

Comments

@rhuss
Copy link
Contributor

rhuss commented Jun 15, 2021

Many development clusters use a self-signed certificate, that should be supported (which is not right now).
@cardil cardil mentioned this issue Jun 26, 2021
Open
@embano1
Copy link

embano1 commented Jun 27, 2021

+1, eg something like —insecure or —insecure-tls

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 26, 2021
@rhuss
Copy link
Contributor Author

rhuss commented Sep 27, 2021

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 27, 2021
@cardil
Copy link
Contributor

cardil commented Dec 22, 2021

This should be supported for in-cluster-sender as well.

@cardil
Copy link
Contributor

cardil commented Dec 22, 2021

I like the HTTPie approach of using single flag --verify. You could skip verification, or to pass a CA-BUNDLE file. See: https://httpie.io/docs/cli/server-ssl-certificate-verification

@cardil cardil mentioned this issue Jan 19, 2022
Closed
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 23, 2022
@rhuss
Copy link
Contributor Author

rhuss commented Mar 24, 2022

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 24, 2022
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 23, 2022
@rhuss
Copy link
Contributor Author

rhuss commented Jun 30, 2022

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 30, 2022
@cardil
Copy link
Contributor

cardil commented Jul 19, 2022

/triage accepted

@knative-prow knative-prow bot added the triage/accepted Issues which should be fixed (post-triage) label Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rhuss @cardil @embano1 @knative-prow-robot