Add support for custom HTTP port in configuration file?

[natevw]

One of the kids and I are trying to play with our own custom webserver for the PETdisk. The easiest way to do this is on a machine or VM on the LAN using a high-numbered (unprivileged) port like 8080.

I noticed however that the config parsing doesn't look for a : separator and instead port 80 is hardcoded in the HTTP client.

We were able to work around this with a port forward on our router, and there's probably other tricks available using ssh or nginx proxies or similar, but it would be convenient if a custom port number could be configured.

(Just browsing it in GitHub without the aid of an IDE, I couldn't 100% trace through how the host thing is handled with the offset but I think it might just be a matter of adding a port field around setUrlData assuming there's some sort of atoi conversion routine handy? Maybe I'll try a stab at it but always takes me a bit to set up each different toolchain and such.)