I just pushed out a new release of Graffiti.Redirect with a couple minor fixes and one big fix.
A couple weeks ago I was talking with Rob Bazinet about moving his blog to Graffiti and I told him he should use my plugin to redirect his old blog to his new blog. He tried it out and ran into a couple problems so he checked out the code and found a huge block of ugly code I had written to append default.aspx to requests, he tried deleting that entire piece of code and just using the simple redirect and everything still worked. On top of everything still working it fixed a couple of annoying bugs.
It turns out that code is only needed for IIS5 and not needed for IIS6+, it has to do with how wild-card request handling is done. I was doing my testing on XP with IIS 5 so I had to write the code to get it working, but since I am deploying on IIS6 I don’t need it either. So I decided to keep Rob’s change and drop IIS 5 support from the plugin, I doubt many people are using IIS5 and if they are they can still download the old version and fix the bugs themselves.
I am thrilled to have a leaner code base and even more thrilled to have a couple annoying bugs fixed, I love open source.
-James
{ 5 comments }
Have you thought of having this placed on the Graffiti marketplace?
I might once I get it out of beta, I don’t want to put it out there and have people run into lots of issues. Of course I haven’t seen what the requirements are to get into the marketplace either… so we will see.
Hi James,
Will the redirect work for certain subfolders of subfolders?
I have Community Server 2007 installed in "/cs", so I’d want to redirect any requests for "/cs/blogs/mabster" but not for, say, "/cs/forums".
Is that sort of thing possible?
Cheers,
Matt
Yes, it should handle that just fine, anything regex can do this thing can re-direct.
Awesome – I’ll give it a whirl. Thanks James!
Comments on this entry are closed.