Skip to content

Hostname is not respected when tls options are specified #953

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

Closed
warenix opened this issue Apr 9, 2020 · 4 comments · Fixed by #2588
Closed

Hostname is not respected when tls options are specified #953

warenix opened this issue Apr 9, 2020 · 4 comments · Fixed by #2588

Comments

@warenix
Copy link

warenix commented Apr 9, 2020

Version

❯ webdev --version
2.5.6

Issue

hostname 0.0.0.0 is working when it's alone.

❯ webdev serve --hostname 0.0.0.0 web:8080
[INFO] Reading cached asset graph completed, took 466ms
[INFO] Checking for updates since last build completed, took 1.5s
[INFO] Serving `web` on http://0.0.0.0:8080
[INFO] Running build completed, took 575ms
[INFO] Caching finalized dependency graph completed, took 322ms
[INFO] Succeeded after 910ms with 0 outputs (0 actions)

But localhost is used instead of the hostname 0.0.0.0 specified

❯ webdev serve --hostname 0.0.0.0 --tls-cert-key mydomain/privkey1.pem --tls-cert-chain mydomain/fullchain1.pem web:8080
[INFO] Reading cached asset graph completed, took 448ms
[INFO] Checking for updates since last build completed, took 1.4s
[INFO] Serving `web` on https://127.0.0.1:8080
[INFO] Running build completed, took 554ms
[INFO] Caching finalized dependency graph completed, took 299ms
[INFO] Succeeded after 865ms with 0 outputs (0 actions)

Expectation

Respect the hostname value when --hostname, --tls-cert-key and --tls-cert-chain are used together.

@warenix warenix changed the title hostname is not respected when tls options are specified Hostname is not respected when tls options are specified Apr 9, 2020
@chrisnorman7
Copy link

I'm seeing the same issue on webdev 2.5.8, with Dart VM version: 2.8.4 (stable) (Unknown timestamp) on "linux_x64".

@Nliver
Copy link

Nliver commented Sep 14, 2021

I also got it , feeling sad

@caybear
Copy link

caybear commented Jun 13, 2023

A very small change to address this issue #2143

@pisabev
Copy link

pisabev commented Oct 29, 2023

This is still open? This - #2143 seems to fix it. Why not merge ?

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 a pull request may close this issue.

5 participants