We want to migrate from WSS2003 to Moss 2007 hosted in a completely different server based on site collection.We will gradually move site collection wise. After moving the site collections of 2003 to Moss I want to redirect the users who type the 2003 site collection url to Moss 2007 site collection url. For this to happen I am using Custom ISAPI filter dll and defining the rewrite rules for the same But the in built-in WSS "stsfltr" is running first. Thatâs why I am not able to get the complete sitecollection url by the time request comes to my custom ISAPI filter. Eg: Requested Url :http://server/sitecoll/_layouts/1033/settings.aspx Changed to :http://server/_layouts/1033/settings.aspx when it comes to my custom ISAPI filter Because of the above behaviour I am not able to redirect url based on site collection level Can you suggest me a solution for this.
On Oct 10, 8:18 am, John Paul <John P...@discussions.microsoft.com> wrote: > We want to migrate from WSS2003 to Moss 2007 hosted in a completely different > server based on site collection.We will gradually move site collection wise. > > After moving the site collections of 2003 to Moss I want to redirect the > users who type the 2003 site collection url to Moss 2007 site collection url. > > For this to happen I am using Custom ISAPI filter dll and defining the > rewrite rules for the same > > But the in built-in WSS "stsfltr" is running first. That's why I am not > able to get the complete sitecollection url by the time request comes to my > custom ISAPI filter. > > Eg: Requested Url :http://server/sitecoll/_layouts/1033/settings.aspx > Changed to :http://server/_layouts/1033/settings.aspx when it comes > to my custom ISAPI filter > > Because of the above behaviour I am not able to redirect url based on site > collection level > > Can you suggest me a solution for this. If you want your filter to run before stsfltr, then make sure your filter: 1. Has same or higher priority than that filter 2. Ordered above/in-front of the filter at the same scope (global or site) //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang //
Thanks for the reply. I did try out the above options you mentioned. I have used the source code provided by CodePlex http://www.codeplex.com/IIRF and made sure on Preprocessor event redirection should happen. But this code is not working for me. Since i am not familiar with c++ i am finding it difficult to do proper implemenation. If you can suggest any existing ISAPI filters which serves this purpose it would be greatful -John
On Oct 12, 5:41 am, johnpaul1...@gmail.com wrote: > Thanks for the reply. > > I did try out the above options you mentioned. I have used the source > code provided by CodePlexhttp://www.codeplex.com/IIRFand made sure > on Preprocessor event redirection should happen. > > But this code is not working for me. Since i am not familiar with c++ > i am finding it difficult to do proper implemenation. > > If you can suggest any existing ISAPI filters which serves this > purpose it would be greatful > > -John If you are not familiar with C++ then you cannot try out both things that I mentioned (which are required for an ISAPI Filter to work in your situation). You just need to verify one line of code and one line in IIS configuration. I'm pretty certain one of them is not set correctly. If you cannot do this, then the only way you can get something working is if someone hands you a filter that they know works. I do not know of any. //David http://w3-4u.blogspot.com http://blogs.msdn.com/David.Wang //
