<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SharePoint 2007 redirect solved: using 301 instead of 302 redirects</title>
	<atom:link href="http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/</link>
	<description>Innovation Matters &#124; SharePoint Server MVP &#124; ISSN 2210-9390</description>
	<lastBuildDate>Fri, 10 Feb 2012 18:00:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: 301 vs 302 Redirects in SharePoint &#171; SPMatt</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-117742</link>
		<dc:creator>301 vs 302 Redirects in SharePoint &#171; SPMatt</dc:creator>
		<pubDate>Wed, 18 Jan 2012 14:51:31 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-117742</guid>
		<description>[...] to write a custom HttpModule to perform the 301 redirect as per Waldek Mastykarz&#8217;s post on Using 301 instead of 302 redirects. Waldek&#8217;s post is focussing more on another MOSS 302 redirect phenomenon rather than the [...]</description>
		<content:encoded><![CDATA[<p>[...] to write a custom HttpModule to perform the 301 redirect as per Waldek Mastykarz&#039;s post on Using 301 instead of 302 redirects. Waldek&#039;s post is focussing more on another MOSS 302 redirect phenomenon rather than the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stjepan</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-29593</link>
		<dc:creator>Stjepan</dc:creator>
		<pubDate>Tue, 06 Oct 2009 07:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-29593</guid>
		<description>@Waldek, thanks for a fast reply!
I did use UrlRewritingNet.UrlRewrite in some other ASP.NET 2.0 web apps but not within Sharepoint. I thought that Sharepoint had some feature for this on its own.
I&#039;ll try implementing the technique you suggested. Thanks again.</description>
		<content:encoded><![CDATA[<p>@Waldek, thanks for a fast reply!<br />
I did use UrlRewritingNet.UrlRewrite in some other ASP.NET 2.0 web apps but not within Sharepoint. I thought that Sharepoint had some feature for this on its own.<br />
I&#039;ll try implementing the technique you suggested. Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Waldek Mastykarz</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-29555</link>
		<dc:creator>Waldek Mastykarz</dc:creator>
		<pubDate>Mon, 05 Oct 2009 14:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-29555</guid>
		<description>@Stjepan: You could try URL Rewriting .NET (http://www.urlrewriting.net/149/en/home.html). If I&#039;m right it allows you to define static redirects.</description>
		<content:encoded><![CDATA[<p>@Stjepan: You could try URL Rewriting .NET (<a href="http://www.urlrewriting.net/149/en/home.html" rel="nofollow">http://www.urlrewriting.net/149/en/home.html</a>). If I&#039;m right it allows you to define static redirects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stjepan</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-29554</link>
		<dc:creator>Stjepan</dc:creator>
		<pubDate>Mon, 05 Oct 2009 12:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-29554</guid>
		<description>Hi,

How to do a 301 Redirect on actuall pages in Sharepoint? For ex. if my current page is http://mydomain.com/pages/page1.aspx and I change the name of it to http://mydomain.com/pages/lorem-ipsum.aspx, how/where do I make this 301 Redirect? So far I have seen, is that I could keep the old page and make it of a type Redirect Page, pointing to my newly created page. But this is not an option for me.
Is it possible to do a propper 301 redirect for pages?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>How to do a 301 Redirect on actuall pages in Sharepoint? For ex. if my current page is <a href="http://mydomain.com/pages/page1.aspx" rel="nofollow">http://mydomain.com/pages/page1.aspx</a> and I change the name of it to <a href="http://mydomain.com/pages/lorem-ipsum.aspx" rel="nofollow">http://mydomain.com/pages/lorem-ipsum.aspx</a>, how/where do I make this 301 Redirect? So far I have seen, is that I could keep the old page and make it of a type Redirect Page, pointing to my newly created page. But this is not an option for me.<br />
Is it possible to do a propper 301 redirect for pages?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Waldek Mastykarz</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-27716</link>
		<dc:creator>Waldek Mastykarz</dc:creator>
		<pubDate>Thu, 10 Sep 2009 10:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-27716</guid>
		<description>@Michael: you&#039;re absolutely right. Although the approach I described is quite flexible it has some serious limitations - just like you&#039;ve mentioned. In a real-life scenario, when you know what kind of site you&#039;re working with, you can skip some of the checks and assume things like the site is a Publishing Site or the Welcome Page is always default.aspx. These little things should definitely improve the performance of your redirect solution.</description>
		<content:encoded><![CDATA[<p>@Michael: you&#039;re absolutely right. Although the approach I described is quite flexible it has some serious limitations &#8211; just like you&#039;ve mentioned. In a real-life scenario, when you know what kind of site you&#039;re working with, you can skip some of the checks and assume things like the site is a Publishing Site or the Welcome Page is always default.aspx. These little things should definitely improve the performance of your redirect solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael HOfer</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-27713</link>
		<dc:creator>Michael HOfer</dc:creator>
		<pubDate>Thu, 10 Sep 2009 09:42:45 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-27713</guid>
		<description>Hi Waldek,

while your solutioln is logical and very well structured, it has one huge disadvantage: performance. I&#039;ve been working in a large intranet project where performance was one of the main concerns. Using the SharePoint publishing API, especially &quot;IspublishingWeb&quot;, &quot;IsPublishingPage&quot; etc. and of course the use of SPSite and SPWeb has turned out to be a complete performance breaker.
I don&#039;t know if you&#039;ve tested your solution with some load tests, but i assume it will be rather slow if 30 or more users are shooting at the same time for the website.

I adressed this topic with an HTTP-Handler that is using the path &quot;/&quot;. So if someone comes on &quot;http://intranet/&quot;, the handler fires. I&#039;ve copied Microsoft&#039;s logic from VariationRoot.aspx and perform the redirect to the correct page directly in the handler. It is ultra-fast and doesn&#039;t need any &quot;costly&quot; Sharepoint objects!

If you have more questions about the solution - just let me know!</description>
		<content:encoded><![CDATA[<p>Hi Waldek,</p>
<p>while your solutioln is logical and very well structured, it has one huge disadvantage: performance. I&#039;ve been working in a large intranet project where performance was one of the main concerns. Using the SharePoint publishing API, especially &#034;IspublishingWeb&#034;, &#034;IsPublishingPage&#034; etc. and of course the use of SPSite and SPWeb has turned out to be a complete performance breaker.<br />
I don&#039;t know if you&#039;ve tested your solution with some load tests, but i assume it will be rather slow if 30 or more users are shooting at the same time for the website.</p>
<p>I adressed this topic with an HTTP-Handler that is using the path &#034;/&#034;. So if someone comes on &#034;http://intranet/&#034;, the handler fires. I&#039;ve copied Microsoft&#039;s logic from VariationRoot.aspx and perform the redirect to the correct page directly in the handler. It is ultra-fast and doesn&#039;t need any &#034;costly&#034; Sharepoint objects!</p>
<p>If you have more questions about the solution &#8211; just let me know!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Waldek Mastykarz</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-24068</link>
		<dc:creator>Waldek Mastykarz</dc:creator>
		<pubDate>Thu, 16 Jul 2009 18:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-24068</guid>
		<description>@Geert: great to hear you find it useful. Thank you for posting the updated regex</description>
		<content:encoded><![CDATA[<p>@Geert: great to hear you find it useful. Thank you for posting the updated regex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geert</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-24032</link>
		<dc:creator>Geert</dc:creator>
		<pubDate>Thu, 16 Jul 2009 09:37:08 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-24032</guid>
		<description>Hi Waldek,

First of all, thanks for your code. I did however find a link on the &#039;Site Settings&#039; page that didn&#039;t work anymore after running the compiled dll. It was &#039;Master Pages and Page Layouts&#039;, because it ends with a / in the querystring, but not followed by a page: http://.../_Layouts/RedirectPage.aspx?Target={SiteCollectionUrl}_catalogs/masterpage.

The regex doesn&#039;t match while actualy it should, since the requestURL does end with a page (RedirectPage.aspx). Possibly there are more links like this one so to avoid this problem I updated the Regex to:
^https?://.*(?/[^/]+\.[^/\.]+(\?.+=.+)?)$

Works fine now.</description>
		<content:encoded><![CDATA[<p>Hi Waldek,</p>
<p>First of all, thanks for your code. I did however find a link on the &#039;Site Settings&#039; page that didn&#039;t work anymore after running the compiled dll. It was &#039;Master Pages and Page Layouts&#039;, because it ends with a / in the querystring, but not followed by a page: <a href="http://.../_Layouts/RedirectPage.aspx?Target=" rel="nofollow">http://&#8230;/_Layouts/RedirectPage.aspx?Target=</a>{SiteCollectionUrl}_catalogs/masterpage.</p>
<p>The regex doesn&#039;t match while actualy it should, since the requestURL does end with a page (RedirectPage.aspx). Possibly there are more links like this one so to avoid this problem I updated the Regex to:<br />
^https?://.*(?/[^/]+\.[^/\.]+(\?.+=.+)?)$</p>
<p>Works fine now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Waldek Mastykarz</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-8623</link>
		<dc:creator>Waldek Mastykarz</dc:creator>
		<pubDate>Tue, 18 Nov 2008 20:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-8623</guid>
		<description>@drew: Name is the unique name of the module you can define yourself and type points to the class name (including namespace).</description>
		<content:encoded><![CDATA[<p>@drew: Name is the unique name of the module you can define yourself and type points to the class name (including namespace).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: drew</title>
		<link>http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/comment-page-1/#comment-8615</link>
		<dc:creator>drew</dc:creator>
		<pubDate>Tue, 18 Nov 2008 17:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://mastykarz.nl/blog/2008/01/21/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/#comment-8615</guid>
		<description>Where does the value name= in your web.config come from?</description>
		<content:encoded><![CDATA[<p>Where does the value name= in your web.config come from?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

