Classics ASP IIS 6.0 how to implement url rewrite? - iis

This is a shared hosting environment running on Windows Server 2003. I want to integrate url rewriting,so below translates:
example.com/product-name-color-ID ===> example.com/product?id=ID
Custom 404 page technique seems easiest way for me but how can i do that?

Instead of a custom 404 hack, check out Helicon Ape. It lets you use an .htaccess file (like Apache) for URL rewriting.

Related

Plesk ignores .htaccess file

I am very new to URL re-writting and I am using Plesk which is Windows based web server and hence I cant use Apache's mod_Rewrite.. can anyone tell me steps for this to happen?
Try ISAPI Rewrite for IIS. It supports mod_rewrite rules of Apache and it is supported by Plesk.
Maybe too late for OP but it might be useful for anyone coming across this. If URL Rewrite is installed in IIS then you can follow this guide to translate htaccess into web.config.
It worked with my case, running PHP website in a shared hosting with Plesk and IIS under ISAPI

301 redirect remote management

Is there a good way of remotely managing 301 redirects in IIS? I have recently taken ownership of a small retail ASP.NET website I've been tasked with providing our SEO provider the ability to change redirects for old products etc without having direct access to the server, or needing us to make the change.
The website is ASP.NET 4.0, running on Windows Server 2008 with IIS 7.
you could maintain a list of the required redirects via an app.config file - have a module which takes the request and checks the request against the file
if there is a match then you could redirect to a known place. The trouble is that it could be a little slow - instead of a config file you could store the redirects in the database as an alternative

seo friendly urls not recognised by IIS

I have a php based site hosted on a IIS server. URL like http://host.net/t.php works but
without the php extension does not work. This site was working properly on a LINUX server previously. ISAPI rewrite Life version was installed on the IIS server. But the problem still persists.
IIS versions prior to 7.x doesn't support extension-less URLs without some ISAPI filter.
This is the reason ;)
EDIT:
Read this blog post:
http://thebackshop.posterous.com/extensionless-urls-with-sitecore-using-the-he
Was it useful for you? Good luck! :)
The problem was resolved by installing IIRF Rewrite 3 module.

Upgraded IIS. Now :80 is appended to all urls sent to isapi rewriter

We recently upgraded from IIS 5.0 and windows 2000 to IIS 7 and windows 2008. For handling url rewrites, we use Helicon Isapi Rewrite 3.
With the new configuration, our rewrite rules are failing because IIS is appending a :80 to our links.
For instance, on the old site.
/media/hr/pdf/application.pdf would redirect to our static server just fine.
On the new site, /media/hr/pdf/application.pdf generates a 404 saying that
:80/media/hr/pdf/application.pdf could not be found.
here is the rule.
RewriteRule (^|^/)(media/.*) http://static.mysite.com/global/images/$2 [NC,L,O]
Does anyone know a way to stop the :80 from being added?
thanks in advance.
I don't know, but....
you can use the built-in IIS7 rewriting module from Microsoft. It's free. It's more commonly used that Helicon's. There's a capability for slurping in rules that are compatible with Apache mod_rewrite, which I think is the same as the syntax for Helicon. Consider it. Find it at http://iis.net
Also - there's a free, open source rewriter that works with IIS7, called IIRF. It won't add :80 to your URLs. Find it at http://iirf.codeplex.com

Apache's ErrorDocument directive for asp/IIS?

now i saw a very good php script and i rewrite it to asp
the script here:Fantastic Animation PHP/CSS/jQuery Error pages
but know iam in big problem
how i can use .htaccess in asp
see how it work
ErrorDocument 500 /error.php?code=500
can i use .htaccess in asp
please tell me because iam newbie in it
because know i convery error.php to error.asp
.htaccess is a web server thing (primarily Apache), not a PHP or ASP thing. If you have your system set up that Apache serves ASP pages (passing through to IIS or using another ASP interpreter), sure, you can use .htaccess with it. But if you're using IIS directly, IIS has its own mechanism for doing things like mapping error pages and such.

Resources