need some help with node-http-proxy

[john.tiger]

we've been using node-http-proxy with the proxy table for handling
several node based websites on a single server - it's been great.

but we need some help for a few other fairly simple applications (it
would be nice to create a node-http-proxy cookbook or how-to)

1) our proxy table routes sites to different ports which their node apps
are configured to - but what about a non node app (just uses html5)

router: {
'nodeapp1.com': '127.0.0.1:8020',
'htmlapp1.com': ?? if this is assigned a port, how does the html
5 app tie to that port ?

2) doing a cross-domain get and post ? ie. using couchdb on port 5984

3) using and testing the server setup on a local dev machine - do we do
something like

router: {
'localnodeapp1.com': '127.0.0.1:8020',
'localhtmlapp1.com': ?? if this is assigned a port, how does the
html 5 app tie to that port ?

then in the browser run/test the app using http://localnodeapp1.com

any help ?

[Ryan Schmidt]

On Oct 3, 2012, at 23:17, john.tiger <john.tig...@gmail.com> wrote:

> 1) our proxy table routes sites to different ports which their node apps are configured to - but what about a non node app (just uses html5)
>
> router: {
> 'nodeapp1.com': '127.0.0.1:8020',
> 'htmlapp1.com': ?? if this is assigned a port, how does the html 5 app tie to that port ?

nodejs is a server-side technology, often used for delivering web content (html, css, javascript, images, etc) to a client.

What is the server-side technology delivering your "html 5 app" to the client? Surely it runs an HTTP server on a specific TCP port number.