Re: [nodejs] is there a non-traumatic way to approach this: http-proxy + a static file server target

Hi Alex, Sam, Thank you for your input. If your vendor documentation uses relative links, it should work as is. i don't think so due to the additional URL path /vendor/FOO introduced at the proxy as in: https://proxyHostFQDN:proxyPort/vendor/FOO When the routing proxy passes the usual

Re: [nodejs] is there a non-traumatic way to approach this: http-proxy + a static file server target

Here are some options, sorted by, in my opinion, the more viable and easy solutions first: 1. Use subdomains, as Alex proposed No modification to the source files, which means it could be easily updated when you vendor updates it. 2. Add an HTML base

[nodejs] is there a non-traumatic way to approach this: http-proxy + a static file server target

Hi, A few days back we received vendor FOO's documentation in electronic format and we put the document root at /path/to/vendor/FOO/doc/root With node-static and the usual: var static = require('node-static'); var file = new static.Server('/path/to/vendor/FOO/doc/root'); ... we

Re: [nodejs] is there a non-traumatic way to approach this: http-proxy + a static file server target

 If your vendor documentation uses relative links, it should work as is. But I guess it's not the case. I'd suggest to place it on a subdomain instead.  07.02.2014, 09:24, "ming" hseum...@gmail.com:Hi,A few days back we received vendor FOO's documentation in electronic format and we put the