Facebook
Twitter
D
dahkness
Guest
Hello all, Glad to be posting here. My name is Marc and I am a network administrator for a company that uses plesk for windows 7.0 on a windows 2k3 box.
I have an issue. We are using virtual domains; we have 1 site setup in IIS, which has all the virtual dirs for the hosted domains.
The client is using .NET, to grab the url of the custom 404 and create dynamic content.
We need to setup a 404 error custom page to go to a dynamic .aspx page. if we do the full path as "File 404" it won't work because asp won't process.
I know asp will process using a relative URL like /dynamic.aspx, BUT the site the domain is on is a virtual dir of the main domain in IIS.
This means that when IIS sees /dynamic.aspx as a 404 URL, then it will look in:
C:\Inetpub\vhosts\default\htdocs\ for the dynamic.aspx page, since this is the root of the main site.
not in:
C:\Inetpub\vhosts\rollover.com\httpdocs\
which is the right dir. Any ideas on how to fix this?
I have an issue. We are using virtual domains; we have 1 site setup in IIS, which has all the virtual dirs for the hosted domains.
The client is using .NET, to grab the url of the custom 404 and create dynamic content.
We need to setup a 404 error custom page to go to a dynamic .aspx page. if we do the full path as "File 404" it won't work because asp won't process.
I know asp will process using a relative URL like /dynamic.aspx, BUT the site the domain is on is a virtual dir of the main domain in IIS.
This means that when IIS sees /dynamic.aspx as a 404 URL, then it will look in:
C:\Inetpub\vhosts\default\htdocs\ for the dynamic.aspx page, since this is the root of the main site.
not in:
C:\Inetpub\vhosts\rollover.com\httpdocs\
which is the right dir. Any ideas on how to fix this?
