You can also use the GUI to build these rewrite rules same thing either way. Or, if you prefer to use the www prefix, you can do that too: Here’s the IIS7 rule to remove the file under / / htaccess format everyone already knows, but oh well. It’d be nicer still if we could just use the. The new rewrite GUI makes it fairly easy to set this stuff up there’s even an import option where you can pull in existing Apache format. We’re using IIS7 with the brand spanking new (and wildly overdue) official Microsoft URL rewriting add-on. Now that we’ve chosen, we need to enforce that choice through URL rewriting. That’s a bit of a downer, but our use of cookies should be quite minimal, so I’m OK with that tradeoff. Using a non-www-version of a webpage will lead to setting cookies for the whole domain, thus making cookieless domains (for example for fast cdn-like access of static resources like css, js and images) impossible. OVERFLOW EPISODE 1 (ENGLISH DUB), Southeast Asias leading anime, comics, and games (ACG) community where people can create, watch and share engaging videos. The only downside of this choice that I can see is that setting cookies for a prefixless domain sets them across all subdomains, as noted by Stecki in the comments of my original blog post on this topic: So, for stackoverflow, we’re going with plain old, and dropping the www prefix. Some people become very religious about whether URLs should have a Me, I’m a bit more sanguine: I think you need to choose your allegiance early in the lifecycle of your website, and stick to it. Where do you stand on The Great Dub-Dub-Dub Debate?
0 Comments
Leave a Reply. |