Virtual Directory, Classic ASP and ASP.NET
3 posts
• Page 1 of 1
Virtual Directory, Classic ASP and ASP.NET
Hi there,
We have been using ISAPI Rewrite 2 (registered version) for the past 7 or 8 years, and currently its running smoothly on our existing site hosted on a Windows 2008 R2 server, running IIS 6.1.
We are currently in the process of upgrading our site from Classic ASP, to ASP.NET - And have some virtual directories, that will not be converted to ASP.NET yet. Therefore we would like the Virtual directories to be handled by ISAPI Rewrite 2.
Our current setup is:
Site
virtual_site1
virtual_site2
virtual_site3
virtual_site4
The folder structure for this is:
Our new site has the same site structure, but the folder structure has the virtual directories pointed at their existing location, thus:
When I look at the IIS Manager, the ISAPI filters are attached the the parent site (http://www.site.com and new.site.com) not the actual virtual directory.
Each of the virtual directories have the httpd.ini files inside of them, and when loading the first page (eg. http://www.site.com/virtual_site1) the page renders fine. But when I request /virtual_site/folder/folder/pagename/ i get an error 404. Requesting the actual /virtual_site/pagename.asp?parameter=123 it works.
Is the ISAPI redirect 2.x compatible with our setup, or do we need to upgrade for this functionality, and if upgrading - Will that be compatible with 2.x - Or will every site hosted be upgraded to version 3?
We have been using ISAPI Rewrite 2 (registered version) for the past 7 or 8 years, and currently its running smoothly on our existing site hosted on a Windows 2008 R2 server, running IIS 6.1.
We are currently in the process of upgrading our site from Classic ASP, to ASP.NET - And have some virtual directories, that will not be converted to ASP.NET yet. Therefore we would like the Virtual directories to be handled by ISAPI Rewrite 2.
Our current setup is:
Site
virtual_site1
virtual_site2
virtual_site3
virtual_site4
The folder structure for this is:
- Code: Select all
D:\www.site.com
D:\www.site.com\virtual_site1
D:\www.site.com\virtual_site2
D:\www.site.com\virtual_site3
D:\www.site.com\virtual_site4
Our new site has the same site structure, but the folder structure has the virtual directories pointed at their existing location, thus:
- Code: Select all
D:\new.site.com
D:\www.site.com\virtual_site1
D:\www.site.com\virtual_site2
D:\www.site.com\virtual_site3
D:\www.site.com\virtual_site4
When I look at the IIS Manager, the ISAPI filters are attached the the parent site (http://www.site.com and new.site.com) not the actual virtual directory.
Each of the virtual directories have the httpd.ini files inside of them, and when loading the first page (eg. http://www.site.com/virtual_site1) the page renders fine. But when I request /virtual_site/folder/folder/pagename/ i get an error 404. Requesting the actual /virtual_site/pagename.asp?parameter=123 it works.
Is the ISAPI redirect 2.x compatible with our setup, or do we need to upgrade for this functionality, and if upgrading - Will that be compatible with 2.x - Or will every site hosted be upgraded to version 3?
Re: Virtual Directory, Classic ASP and ASP.NET
I do not completely understand your setup at this moment.
Could you explain how these directories are mapped to the IIS web sites?
For example:
etc.
Also, show your exiting rules and a request URI that do not work, please.
Could you explain how these directories are mapped to the IIS web sites?
For example:
- Code: Select all
D:\www.site.com -> http://www.site.com/ (IIS site 1),
D:\www.site.com\virtual_site1 -> http://www.site.com/virtual_site1/ (IIS site1 subdir),
D:\new.site.com\ -> http://new.site.com/ (IIS site 2),
etc.
Also, show your exiting rules and a request URI that do not work, please.
- tidaltides
-
- Posts: 24
- Joined: 27 Nov 2012, 21:57
Re: Virtual Directory, Classic ASP and ASP.NET
Is this the one that works with and without HTTPS?
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 0 guests