

If you wish to list/modify your existing Virtual Directories, you may do so by following the below mentioned process:
Tags: Anonymous User, Click Manage Web Hosting Service, Control Panel, Details View, Directory Manager, Domain Name, Drop Down Menu, Management Interface, Manager Gt, Virtual Directories, Virtual Directory, Virtual Directory Manager, Web Hosting package, Web Hosting Service, Website Directory, Website Management
Follow the below mentioned process to add a Virtual Directory for your .NET Application:
Tags: Anonymous User, Application Login, Checkbox, Click, Control, Control Panel, Details View, Directory Manager, Domain Name, Drop Down Menu, Framework Version, Management Interface, Net Control, Virtual Directory, Web Hosting Service, Website Directory, Website Management
If for some reason, you wish to delete your existing Virtual Directory, you may do so by following the below mentioned process:
A Virtual Directory with .NET Framework version 1.1 and no write permissions for the IIS (anonymous) User is created for the web folder by default. You cannot delete this Virtual Directory. You may however -
Click here to read how to perform either of the above mentioned actions >>
Tags: Anonymous User, Click, Confirmation, Control Panel, Delete, Delete Directory, Details View, Directory Manager, Domain Name, Framework Version, Management Interface, Manager Gt, Net Framework, Pop Up Window, Virtual Directories, Virtual Directory, Web Folder, Web Hosting Service, Website Directory, Website Management
The Microsoft IIS 6.0 web server considers relative paths as a potential security hazard and therefore disables the same by default. To ensure that the server where your website is hosted can not be exploited in this fashion, Gossimer keeps relative paths disabled.
Examples
Relative Path: <img src=”../images/image.gif”>
Absolute Path: <img src=”www.yourdomain.com/images/image.gif”>
If you have designed a website in ASP which uses relative linking, then your website visitors may encounter an error message such as:
Active Server Pages, ASP 0131
Disallowed Parent Path
The Include file ‘../<filename.ext>’ cannot contain ‘..’ to indicate the parent directory.
/<path>/<filename.asp>, line <number>
OR
Server.MapPath()error ‘ASP 0175 : 80004005′ Disallowed Path Characters
You would receive such errors because you are referring to a file in a directory, which is a level above your Current Working Directory using Relative Paths or better know as Parent Paths.
To resolve this error, you have 2 options:
Option 1: Use an Absolute Path with the domain name
For every file you want to link within your ASP file, you need to mention the complete path including the domain name. For example, http://www.yourdomain.com/images/1.gif.
Option 2: Use an Absolute Virtual Path
You would need to modify your ASP scripts to use absolute virtual paths from the root of your website, instead of relative paths. For example, if you use an include file named “mycode.inc” at the root of your site, the virtual path would be “/mycode.inc.” If you use the same include file in a virtual directory named “/includes” on your server, the virtual path would be “/includes/mycode.inc” where “/” indicates the ROOT of your Website or the Web Directory.
The below example illustrates how to implement Virtual Paths in your scripts instead of Relative Paths -
<!–#include virtual=”/<virtual path>/<filename_you_wish_to_include>”–>
Tags: Absolute Path, Active Server Pages, ASP, Asp Pages, Asp Scripts, Error Asp, Gif, Gossimer, Gt Line, Image Gif, Img Src, Microsoft, Microsoft Iis, Option 1, Relative Path, Relative Paths, Security Hazard, Virtual Directory, Virtual Path, Virtual Paths, Web Directory, Web Server, Website Visitors, www.yourdomain.com/images/image.gif, Yourdomain













