starred/dnss

Fork 0

mirror of https://github.com/albertito/dnss.git synced 2026-04-26 18:05:57 +03:00

[GH-ISSUE #8] Is the flag -testing__insecure_http just for testing? #7

New issue

Closed

opened 2026-03-02 23:35:54 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 23:35:54 +03:00

Owner

Originally created by @triatic on GitHub (Jul 19, 2020).
Original GitHub issue: https://github.com/albertito/dnss/issues/8

Originally assigned to: @albertito on GitHub.

Thanks for dnss, very useful!

I use the flag -testing__insecure_http because dnss sits behind encrypted Apache, so I do not need dnss to use encryption.

Is the flag -testing__insecure_http ok to use in this scenario, i.e. not just for "testing"?

Originally created by @triatic on GitHub (Jul 19, 2020). Original GitHub issue: https://github.com/albertito/dnss/issues/8 Originally assigned to: @albertito on GitHub. Thanks for dnss, very useful! I use the flag `-testing__insecure_http` because dnss sits behind encrypted Apache, so I do not need dnss to use encryption. Is the flag `-testing__insecure_http` ok to use in this scenario, i.e. not just for "testing"?

kerem added the

enhancement

question

labels

2026-03-02 23:35:54 +03:00

kerem referenced this issue

2026-03-02 23:35:54 +03:00

[GH-ISSUE #7] Cannot change HTTPS Upstream #8

kerem closed this issue

2026-03-02 23:35:54 +03:00

kerem commented

2026-03-02 23:35:55 +03:00

Author

Owner

@albertito commented on GitHub (Jul 20, 2020):

Thank you!

Yes, in that scenario it is ok. The only thing the flag does is make dnss listen on http instead of https.

That use case is quite reasonable, so maybe I should rename the flag to just --insecure_http or similar. I'll leave this open to track that feature request.

Thanks!

@albertito commented on GitHub (Jul 20, 2020): Thank you! Yes, in that scenario it is ok. The only thing the flag does is make dnss listen on http instead of https. That use case is quite reasonable, so maybe I should rename the flag to just `--insecure_http` or similar. I'll leave this open to track that feature request. Thanks!

kerem commented

2026-03-02 23:35:55 +03:00

Author

Owner

@triatic commented on GitHub (Jul 20, 2020):

Thanks for your reply. Yes, --insecure_http or something else without "testing" seems more appropriate as this is a very useful option for reverse proxy usage behind a secure server and not just for testing.

@triatic commented on GitHub (Jul 20, 2020): Thanks for your reply. Yes, `--insecure_http` or something else without "testing" seems more appropriate as this is a very useful option for reverse proxy usage behind a secure server and not just for testing.

kerem commented

2026-03-02 23:35:55 +03:00

Author

Owner

@albertito commented on GitHub (Jul 28, 2020):

Commit 90210b7a8, currently in the next branch, implements this.

The flag is renamed to insecure_http_server.

I'll move it to the master branch in a few days, assuming there are no issues.

Thanks again!

@albertito commented on GitHub (Jul 28, 2020): Commit 90210b7a8, currently in the `next` branch, implements this. The flag is renamed to `insecure_http_server`. I'll move it to the `master` branch in a few days, assuming there are no issues. Thanks again!

kerem commented

2026-03-02 23:35:56 +03:00

Author

Owner

@albertito commented on GitHub (Jul 29, 2020):

Commit 90210b7 is now in master, so this should be fixed.

Thanks for reporting this!

@albertito commented on GitHub (Jul 29, 2020): Commit 90210b7 is now in `master`, so this should be fixed. Thanks for reporting this!

kerem commented

2026-03-02 23:35:56 +03:00

Author

Owner

@triatic commented on GitHub (Jul 30, 2020):

No problem. I've just downloaded it and I'm using the new flag name. 👍

@triatic commented on GitHub (Jul 30, 2020): No problem. I've just downloaded it and I'm using the new flag name. 👍