First, I’d like to say a big thank you to you and all of the developers. The more I use discourse (about 3 days now of playing with it) the more I really like it.
I wasn’t asking to support custom ports. I was trying to say please don’t have the app store anything other than the path on the server to the item in question. Let the webserver deal with protocol (http/https), hostname(s), and the port(s).
When I pasted the image if the app had only stored “/uploads/path/to/file” then all would have worked if the webserver is setup properly.
I was viewing the site using http://localhost:8080/ and from the little testing I did all worked great, except for the image part.
Wordpress exhibits similar behavior as well, drives me nuts. I’ve seen cases with WP where I upload something using https (as admin was forced to ssl) yet visitors are allowed http including the upload, yet WP stored https for the upload and thus returns an https link back to the browser.
When I deploy discourse in a production role, it’ll be behind a load balancer/reverse proxy (nginx/varnish), so I can probably work up some rules to catch and fix these types of things. Though it’d be nice if apps wouldn’t do this in the first place.