Dont append port 80 to the socketUrl

[Munksgaard]

Intended to fix #2

[wking-io]

Thanks for the PR to fix the problem that you found! Couple of questions before I merge:

What tests did you run to make sure it still works in all expected scenarios? ( Sorry the test suite in this lib is not the best yet! )

Did you test that live reload still works in both http and https?

[Munksgaard]

Thanks for the PR to fix the problem that you found! Couple of questions before I merge:

What tests did you run to make sure it still works in all expected scenarios? ( Sorry the test suite in this lib is not the best yet! )

Did you test that live reload still works in both http and https?

I tested that the live reload worked on both http and https when running through the ngrok tunnel, and it also seems to work when I am accessing my server locally (through http).

The result of my changes is mostly a simplification of what was there before. I don't think it is necessary for the socketUrl to actually have port information in it, which seem to have been the assumption before, but I am not in any way an expert, so it is very possible that there are edge cases I haven't thought about.

[wking-io]

I am also not in anyway an expert haha! I will try and do some research, but if I do not find anything I will merge! :)

[Munksgaard]

I am also not in anyway an expert haha! I will try and do some research, but if I do not find anything I will merge! :)

Sounds good. Thanks for your work, elm-serve (and elm-live) are great tools to work with :-)

[Munksgaard]

Any progress on this?

[wking-io]

Yeah researched and asked around and as far as I could tell it would not be a problem. Seems websocket ports fill automatically. So I guess we will find out! 👍