Malformed URL when setting external artefact server

[vikanezrimaya]

When I set LAMINAR_ARCHVE_URL, my artefact suddenly got a strange URL: http://192.168.1.33:8080/jobs/hello/https://ci.<mydomain.tld>/archive/hello/1/hello-20170922.

I'm accessing Laminar via HTTP because I cannot proxy websockets with my lighttpd server - it lacks mod_websocket to do it, and Laminar is trying to access unsecured socket anyway - but the reason is not important as different URL schemes probably are.

[ohwgiles]

Right, that's probably a bug I introduced moving from angular to vue. I've pushed a fix so that LAMINAR_ARCHIVE_URL is linked properly in the frontend.

I've also pushed a change to the websocket access - it will directly open a secured websocket if it's running under https. Like you say, this depends on support from the reverse proxy.