StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>If you're using ii7 the easiest way to do this is to use the <a href="http://www.iis.net/download/URLRewrite" rel="nofollow noreferrer">URL Rewrite Module</a> According to that link you can</p> <blockquote> <p>Define powerful rules to transform complex URLs into simple and consistent Web addresses</p> <p>URL Rewrite allows Web administrators to easily build powerful rules using rewrite providers written in .NET, regular expression pattern matching, and wildcard mapping to examine information in both URLs and other HTTP headers and IIS server variables. Rules can be written to generate URLs that can be easier for users to remember, simple for search engines to index, and allow URLs to follow a consistent and canonical host name format. URL Rewrite further simplifies the rule creation process with support for content rewriting, rule templates, rewrite maps, rule validation, and import of existing mod_rewrite rules.</p> </blockquote> <p>Otherwise you will have to use the techniques described by Andrew M or use Response.Redirect. In any case I'm fairly certain all of these methods result in a http 301 response. I mention this because its not clear why you don't want to do Response.Redirect. Is this a coding constraint?</p> <p><strong>Update</strong> Since you're using IIS 6 you'll need to use another method for URL rewriting. </p> <p><a href="http://msdn.microsoft.com/en-us/library/ms972974.aspx" rel="nofollow noreferrer">This Article</a> from Scott Mitchell describes in detail how to do it.</p> <blockquote> <p><strong>Implementing URL Rewriting</strong></p> <p>URL rewriting can be implemented either with ISAPI filters at the IIS Web server level, or with either HTTP modules or HTTP handlers at the ASP.NET level. This article focuses on implementing URL rewriting with ASP.NET, so we won't be delving into the specifics of implementing URL rewriting with ISAPI filters. There are, however, numerous third-party ISAPI filters available for URL rewriting, such as:</p> <p><a href="http://www.isapirewrite.com/" rel="nofollow noreferrer">ISAPI Rewrite</a></p> <p><a href="http://www.qwerksoft.com/products/iisrewrite/" rel="nofollow noreferrer">IIS Rewrite</a> </p> <p><a href="http://port80software.com/products/pagexchanger/" rel="nofollow noreferrer">PageXChanger</a></p> <p>And many others!</p> </blockquote> <p>The article goes on to describe how to implement HTTP Modules or Handlers.</p> <p><strong>Peformance</strong> A redirect response HTTP 301 usually only contains a small amount of data < 1K. So I would be surprised if it was noticeable. For example the difference in the page load of these urls isn't noticible</p> <p><a href="https://stackoverflow.com/q/4144940/119477">"https://stackoverflow.com/q/4144940/119477"</a></p> <p><a href="https://stackoverflow.com/questions/4144940/url-rewrite-without-redirect-in-asp-net">"https://stackoverflow.com/questions/4144940/url-rewrite-without-redirect-in-asp-net"</a></p> <p>(I have confirmed using ieHTTPHeaders that http 301 is what is used for the change in URL)</p> <p><strong>Page Rank</strong></p> <p><a href="http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=93633" rel="nofollow noreferrer">This is</a> what google's webmaster central site has to say about 301.</p> <blockquote> <p>If you need to change the URL of a page as it is shown in search engine results, we recommended that you use a server-side 301 redirect. This is the best way to ensure that users and search engines are directed to the correct page. </p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload