Web pointing and virtual directory

[SFX Group]

Hi

Might be a no go already this, however...

GBPVR is : http://server:7647/gbpvr/*
NPVR is : http://server:8866/*

This seems like a nice idea, however as the new server is in the root of the main web server on port 8866 it can no longer be proxy to anywhere without some major MODProxy header re-writes, which are a pain and can sometimes create a nightmare with broken references in pages.

While a server sits inside a virtual container (which was gbpvr/) any proxy control was nice and easy, however while its in the root this means any proxy control breaks everything (such as the promise raid controller server, OWA, backup server) as all the above have a "virtual directory" like /owa and /promise and /myrestore.

This by design was to allow proxy control of the servers, they can all be proxy controlled from one port. However as NPVR looks for everything in the root, no matter which service i need to obtain i get a login for NPVR or file not found (as /owa is not in the NPVR virtual directory).

Is there a way of placing the NPVR webserver inside a virtual container in its own server (like it used to be with GBPVR, now this deos mean you can still redirect the root of 8866 to this container and means it can then be proxy controlled), otherwise i cant see it outside the firewall (without some header re-wrties as it wanders through the proxy server, which i can do, however is bound to break the odd page as every reference needs to be re-written before its passed to the client).

Thanks (not used the new one yet, mainly as cant see it outside of the local network )

[UncleJohnsBand]

Hi

Might be a no go already this, however...

GBPVR is : http://server:7647/gbpvr/*
NPVR is : http://server:8866/*

This seems like a nice idea, however as the new server is in the root of the main web server on port 8866 it can no longer be proxy to anywhere without some major MODProxy header re-writes, which are a pain and can sometimes create a nightmare with broken references in pages.

While a server sits inside a virtual container (which was gbpvr/) any proxy control was nice and easy, however while its in the root this means any proxy control breaks everything (such as the promise raid controller server, OWA, backup server) as all the above have a "virtual directory" like /owa and /promise and /myrestore.

This by design was to allow proxy control of the servers, they can all be proxy controlled from one port. However as NPVR looks for everything in the root, no matter which service i need to obtain i get a login for NPVR or file not found (as /owa is not in the NPVR virtual directory).

Is there a way of placing the NPVR webserver inside a virtual container in its own server (like it used to be with GBPVR, now this deos mean you can still redirect the root of 8866 to this container and means it can then be proxy controlled), otherwise i cant see it outside the firewall (without some header re-wrties as it wanders through the proxy server, which i can do, however is bound to break the odd page as every reference needs to be re-written before its passed to the client).

Thanks (not used the new one yet, mainly as cant see it outside of the local network )

Actually....sub made this change and it is outside of NEWA itself....it is in NPVR itself. The web server also supports all the communication to the NMT devices so I would guess that you will not see this address changing. I had to make a bunch of coding changes myself to accomodate the new setup....but it wasn't to bad.

Personally.....I don't think you should only have one service listening on a port....I have triaged many an issue where people were piggybacking services on the GBPVR port which messed with its operation so I notmally tell people get everything off the GBPVR port (and now the NPVR port) since there can be issues from the shared port usage.

[mvallevand]

The port the NMT calls can be changed via a command line switch if need be.

Martin