Sorry for the late reply. I was away the last few days.
I tested it at home and it worked out-of-the-box. But I was careless. The application I tested at home was a Flask application, while the one at work is a legacy PHP application. That application is an ancient app which is not following a sane development process yet and the situation is as follows:
* The devs connect remote to a dev machine to work on the code.
* There is a DNS entry for this dev box. So while working on the code, the application is accessed via this address (due to virtual hosting).
* A while back, JS has been ported to closure, and the existing process was to compile the code on the dev machine. And not using the "serve" subcommand of plovr.
* Only ports 22 and 80 are open to the dev machine.
Being able to use "serve" in RAW mode is one of the many baby-steps I am taking to get the development process a bit more convenient.
I'm not sure how to fix this in plovr as, in a way it is related to the development process of this particular app. But it effectively prevents us from using "RAW" mode. The best solution I came up with would still be to add a command-line flag to be able to control the hostname when creating "script" tags in RAW mode. Or is there another solution?