url-rewriting

In order to avoid content duplication, I would like to avoid the pages of my site being accessible by several URLs (with or without trailing slash). Currently, the URLs catalog/product/1 and catalog/product/1/ lead to the same page. My goal is that the second URL redirect to the first (redirection 301, of course). None page of my site should be accessible with a trailing slash, except my home page / obviously. What is the best way to do this? Using .htaccess or routes.rb? How would you do that? NB: I'm developing with Ruby on Rails 1.2.3 I'd use Apache's mod_rewrite . Try this: RewriteEngine

I am using Azure Verizon CDN to publish my web application (an SPA) from Blob storage. I've successfully set up a custom domain and SSL. I've added a rewrite rule in the CDN to redirect to the default document index.html. Basically, this takes the incoming request and inserts "index.html" between the URL path and any query strings. So mydomain.com/startup goes to mydomain.com/startup/index.html mydomain.com/homepage goes to mydomain.com/homepage/index.html and mydomain.com/showuser/?userId=xxxxx goes to mydomain.com/showuser/index.html/?userid=xxxxx Which all seems to work well. Existing rule

So the idea is to remove the .html extension from each page like so... www.website.com/File.html > www.website.com/File www.website.com/Folder/File.html > www.website.com/Folder/File Now I've managed to do this using a URL Rewrite, but it means having to write a rewrite for each page, which is time consuming, not efficient and impractical say if the website is more than 20 pages. Is there a way to do this by writing just one or two rewrites in the web.config? This solution worked for me in the end: <rule name="RedirectUserFriendlyURL1" stopProcessing="true"> <match url="^(.*)\.(.*)$" />

Having an issue with my urlrewrites - anytime I point to a page that is to be rewritten it fails to display because it is also applying the rule to the css & js files that are referenced within my webpage. To try and remedy this I put in a fully qualified path to the css and js - this renders fine on any page where the rewrite isnt applied yet when i try to access a rewritten page the browser hangs. Has anyone encountered something similar and if so have you a solution? Appreciate any help. Tried looking on the site at similar issues but none have helped so far. <rewrite> <outboundRules> <rule

I have a AngularJS application that utilizes URL Rewriting for linking. My rewrite rule looks like : <rewrite> <rules> <rule name="MainRule" stopProcessing="true"> <match url=".*" /> <conditions logicalGrouping="MatchAll"> <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" /> <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" /> <add input="{REQUEST_FILENAME}" matchType="Pattern" pattern="^api/(.*)" negate="false" /> </conditions> <action type="Rewrite" url="Default.cshtml" /> </rule> </rules> I found this solution on SO: How do I configure IIS for URL

I am trying to do an invisible (transparent ?) rewrite via .htaccess and the proxy flag. It works with the [R] flag but not with the [P] flag because it just gives a 500 error. The two domains are on separate servers and the mod_proxy module is enabled. Is my .htaccess correct? Options +FollowSymLinks RewriteEngine On RewriteBase / RewriteCond %{HTTP_HOST} =one.com RewriteRule ^(.*)$ http://two.com/$1 [P] If mod_proxy was compiled as a shared module, it requires that you explicitly load the relevant submodules too. It's possible that on your server mod_proxy_http is not enabled, which leads to

I am using Apache Friends XAMPP in Windows (Local Server). I setup the virtual host in httpd-vhosts.conf in an Apache configuration directory like this NameVirtualHost *:80 <VirtualHost *:80> ServerName test.example.com DocumentRoot "E:\xampp\htdocs\example" </VirtualHost> This works fine when I browse the URL http://test.example.com Is it possible to create virtual host from Apache .htaccess dynamically? The context for VirtualHost has to be server config . See the Apache docs . This means that the directive may be used in the server configuration files (e.g., httpd.conf), but not within any