In Magento CE, I&#39;d like to install an add-on to Extendware Page Cache called Lightening Cache.

It requires editing the Apache configuration inside the virtual host definition for the site, by adding:

    RewriteEngine On
    RewriteMap ewpchash prg:/home/.../shell/extendware/ewpagecache/apache/md5.php
    
    RewriteCond %{REQUEST_METHOD} !POST
    RewriteCond %{REQUEST_URI} !\.(js|css|png|jpg|jpeg|ico|gif)$ [NC]
    RewriteCond %{DOCUMENT_ROOT}%{SCRIPT_FILENAME} !-f
    RewriteCond ${ewpchash:%{HTTPS};~;%{HTTP_HOST};~;%{REQUEST_URI};~;%{QUERY_STRING};~;%{HTTP:Cookie};~;%{SCRIPT_FILENAME};~;%{REMOTE_ADDR};~;%{HTTP_USER_AGENT}} -f
    RewriteRule ^(.*)$ ${ewpchash:%{HTTPS};~;%{HTTP_HOST};~;%{REQUEST_URI};~;%{QUERY_STRING};~;%{HTTP:Cookie};~;%{SCRIPT_FILENAME};~;%{REMOTE_ADDR};~;%{HTTP_USER_AGENT}} [NC,L]
    &lt;FilesMatch &quot;\.(html)$&quot;&gt;
         Header unset Cache-Control
         Header unset Expires
         Header append Expires &quot;Thu, 19 Nov 1981 08:52:00 GMT&quot;
         Header append Cache-Control &quot;must-revalidate&quot;
    &lt;/FilesMatch&gt;

I have added this to the bottom of `/etc/apache2/sites-enabled/site.conf`.

When I run the command `apachectl graceful`, I receive the error:

&gt; AH00526: Syntax error on line 53 of
&gt; /etc/apache2/sites-enabled/site.conf: Invalid command &#39;Header&#39;,
&gt; perhaps misspelled or defined by a module not included in the server
&gt; configuration Action &#39;graceful&#39; failed. The Apache error log may have
&gt; more information.

Site is running Apache 2.4

Have I done something wrong?

Apache: edit to .conf file produces &quot;Invalid command &#39;Header&#39;&quot;

I use [**NGINX**][1] in my dedicated server.

I&#39;ve a question about the **return** and **rewrite 301**.


----------


**Rewrite 301:**

    rewrite ^ http://xxx.xxxxx.net/xx-xxx/$request_uri? permanent;

**Return 301:**

    location ~ redirect-this/?$ {
        return 301 http://xxx.xxxxx.net/xx-xxx/redirect-this$1;
    }


----------


All redirects work correctly. But..

**Which is the most effective method to make a 301 redirect?**

I&#39;ve more than 200 url to redirect. So, what you recommend?


  [1]: http://nginx.org/

NGINX - Return 301 vs Rewrite

Best way managing session in Java. I heard that cookies are not reliable option for this as they gets stored into browser and can be accessed later on? Is this correct? If possible please come up with the answers with the coding example.

Which is the best among:

 - **URL Rewriting**: Server will add an additional parameter at the end of URL link
 - **Hidden parameter in Form**: server will add an additional parameter at every form in HTML
 - **cookie**: Server will ask browser to maintain a cookie. 

Best option for Session management in Java

I have some IIS rewrite rules that I want to vary by environment. The development rewrite rules are in the web.config file, then at the end of the web.test.config file I have:

    

        &lt;appSettings&gt;
             ...Some app settings tranforms here
        &lt;/appSettings&gt;
        &lt;system.webserver&gt;
                &lt;rewrite xdt:Transform=&quot;Replace&quot;&gt;
                  &lt;rules&gt;
                    ... rules here
                  &lt;/rules&gt;
                &lt;/rewrite&gt;
              &lt;/system.webserver&gt;
            &lt;/configuration&gt;

My app settings are getting transformed when I deploy to test, but by IIS rewrite rules are not. I was hoping the entire `&lt;rewrite&gt;` section would simply be replaced with the one in the transform file (as per http://msdn.microsoft.com/en-us/library/dd465326.aspx), but nothing is changing.

I have tried putting `xdt:Transform=&quot;Replace&quot; xdt:Locator=&quot;Match(name)&quot;&gt;` on the individual rules too:

    &lt;rule name=&quot;Test rule&quot; stopProcessing=&quot;true&quot; xdt:Transform=&quot;Replace&quot; xdt:Locator=&quot;Match(name)&quot;&gt;

But again this makes no difference.

Is it even possible to replace rewrite rules in the web.config and if so, what am I missing?


Replacing IIS rewrite rules in web.config transform

So I know this may seem a little strange but I for sake of consistency, I would like all my urls to appear in this form: http://domain.com/page/ So far I have gotten the regular pages working but I cannot seem to get the error pages working properly.

If the user visits a page or directory that does not exist, I would like the browser to hard redirect to: http://domain.com/404/ This directory, however, will not actually exist. The real location of the error page will be under /pages/errors/404.php

Also, although I do not need an exact answer for all the various errors (400, 401, 403, 404, 500), I will be applying whatever method is given to redirect all of these to their &quot;proper&quot; URL&#39;s (eg. http://domain.com/400/ http://domain.com/500/ etc.)

Any ideas?

Rewrite URL after redirecting 404 error htaccess

I was planning to use url routing for a Web Forms application. But, after reading some [posts][1], I am not sure if it is an easy approach.

Is it better to use the [URL Rewrite module][2] for web forms? But, it is only for IIS7. Initially, there was some buzz that URL routing is totally decoupled from Asp.Net MVC and it could be used for web forms.

Would love to hear any suggestions..


  [1]: http://learn.iis.net/page.aspx/496/iis-url-rewriting-and-aspnet-routing/
  [2]: http://learn.iis.net/page.aspx/460/using-url-rewrite-module/

IIS URL Rewriting vs URL Routing

We have several rails apps under common domain in Docker, and we use nginx to direct requests to specific apps.

    our_dev_server.com/foo # proxies to foo app
    our_dev_server.com/bar # proxies to bar

Config looks like this:

    upstream foo {
      server foo:3000;
    }

    upstream bar {
      server bar:3000;
    }

    # and about 10 more...

    server {
      listen *:80 default_server;

      server_name our_dev_server.com;

      location /foo {
          # this is specific to asset management in rails dev
          rewrite ^/foo/assets(/.*)$ /assets/$1 break;
          rewrite ^/foo(/.*)$ /foo/$1 break;
          proxy_pass http://foo;
      }

      location /bar {
          rewrite ^/bar/assets(/.*)$ /assets/$1 break;
          rewrite ^/bar(/.*)$ /bar/$1 break;
          proxy_pass http://bar;
      }

      # and about 10 more...
    }

If one of these apps is not started then nginx fails and stops:

    host not found in upstream &quot;bar:3000&quot; in /etc/nginx/conf.d/nginx.conf:6

We don&#39;t need them all to be up but nginx fails otherwise.
How to make nginx ignore failed upstreams?

Setup nginx not to crash if host in upstream is not found

I have 8 lines of rewrite rules in my .htaccess file. I need to exclude two physical directories on my server from these rules, so they can become accessible. For now all requests are sent to index.php file. 

Directories to exclude: &quot;admin&quot; and &quot;user&quot;. 

So http requests: http://www.domain.com/admin/ should not be passed to index.php file.


    ErrorDocument 404 /index.php?mod=error404
    
    Options  FollowSymLinks
    RewriteEngine On
    RewriteBase /
    
    RewriteCond %{HTTP_HOST} !^www\.domain\.com$ [NC]
    RewriteRule ^(.*)$ http://www.domain.com/$1 [R=301,L]
    
    RewriteRule ^([^/] )/([^/] )\.html$ index.php?lang=$1&amp;mod=$2 [L]
    RewriteRule ^([^/] )/$ index.php?lang=$1&amp;mod=home [L]

.htaccess mod_rewrite - how to exclude directory from rewrite rule

I have a URL that looks like:

    url.com/picture.php?id=51

How would I go about converting that URL to:

    picture.php/Some-text-goes-here/51

I think WordPress does the same.

How do I go about making friendly URLs in PHP?

URL rewriting with PHP

Is there a way I can modify the URL of the current page without reloading the page?

I would like to access the portion **before** the # hash if possible.

I only need to change the portion **after** the domain, so it&#39;s not like I&#39;m violating cross-domain policies.

     window.location.href = &quot;www.mysite.com/page2.php&quot;;  // this reloads


How do I modify the URL without reloading the page?

I have the [AngularJS seed project][1] and I&#39;ve added 

    $locationProvider.html5Mode(true).hashPrefix(&#39;!&#39;);
 to the app.js file. I want to configure IIS 7 to route all requests to     

    http://localhost/app/index.html

so that this works for me. How do I do this?

**Update:**

I&#39;ve just discovered, downloaded and installed the [IIS URL Rewrite module][2], hoping this will make it easy and obvious to achieve my goal.


**Update 2**:

I guess this sums up what I&#39;m trying to achieve (taken from the [AngularJS Developer documentation][3]):

&gt; Using this mode requires URL rewriting on server side,
&gt; basically you have to rewrite all your links to entry point of your
&gt; application (e.g. index.html)

**Update 3:**

I&#39;m still working on this and I realise I need to NOT redirect (have rules that rewrite) certain URLs such as 

    http://localhost/app/lib/angular/angular.js
    http://localhost/app/partials/partial1.html

so anything that is in the css, js, lib or partials directories isn&#39;t redirected. Everything else will need to be redirected to app/index.html

Anyone know how to achieve this easily without having to add a rule for every single file?


**Update 4:**

I have 2 inbound rules defined in the IIS URL Rewrite module. The first rule is:

![IIS URL Rewrite Inbound Rule 1][4]

The second rule is:

![IIS URL Rewrite Inbound Rule 2][5]

Now when I navigate to localhost/app/view1 it loads the page, however the supporting files (the ones in the css, js, lib and partials directories) are also being rewritten to the app/index.html page - so everything is coming back as the index.html page no matter what URL is used. I guess this means my first rule, that is supposed to prevent these URLs from being processed by the second rule, isn&#39;t working.. any ideas? ...anyone? ...I feel so alone... :-(


  [1]: https://github.com/angular/angular-seed
  [2]: http://www.iis.net/downloads/microsoft/url-rewrite
  [3]: http://docs.angularjs.org/guide/dev_guide.services.$location
  [4]: http://i.stack.imgur.com/3vFmW.png
  [5]: http://i.stack.imgur.com/e9zKY.png

How do I configure IIS for URL Rewriting an AngularJS application in HTML5 mode?

I need to redirect every http://test.com request to http://www.test.com. How can this be done.

In the server block I tried adding 

    rewrite ^/(.*) http://www.test.com/$1 permanent;

but in browser it says


&gt; The page isn&#39;t redirecting properly
&gt;
&gt; Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

My server block looks like

     server {
                listen       80;
                server_name  test.com;
                client_max_body_size   10M;
                client_body_buffer_size   128k;

                root       /home/test/test/public;
                passenger_enabled on;
                rails_env production;

                #rewrite ^/(.*) http://www.test.com/$1 permanent;
                #rewrite ^(.*)$ $scheme://www.test.com$1;

                error_page   500 502 503 504  /50x.html;
                location = /50x.html {
                        root   html;
                }
        }


How to redirect a URL in Nginx

Currently I am using the hosting with **lightspeed** server. Hosting says `mod_rewrite` is enabled but I can&#39;t get my script working there. Whenever I try to access the URL, it returns **404 - not found** page.

I put the same codes at another server which is running with Apache. It&#39;s working over there. So I guess, it&#39;s the `.htaccess` and `mod_rewrite` issue.

But Hosting support is still insisting with me that their mod_rewrite is on, so I would like to know how can I check whether it&#39;s actually enabled or not.

I tried to check with `phpinfo()`, but no luck, I can&#39;t find `mod_rewrite` there, is it because they are using `lightspeed`?

Is there any way to check? Please help me out. Thank you.

**FYI:** my `.htaccess` code is

    Options -Indexes
    
    &lt;IfModule mod_rewrite.c&gt;
    DirectoryIndex index.php
    RewriteEngine on
    
    RewriteCond $1 !^(index\.php|assets|robots\.txt|favicon\.ico)
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ ./index.php/$1 [L,QSA]
    &lt;/IfModule&gt;

I tried like this also


    DirectoryIndex index.php
    RewriteEngine on
    
    RewriteCond $1 !^(index\.php|assets|robots\.txt|favicon\.ico)
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ ./index.php/$1 [L,QSA]

But same result.

How to check whether mod_rewrite is enable on server?

I&#39;m in the process of reorganizing URL structure. 
I need to setup redirect rules for specific URLs - I&#39;m using Nginx. 

Basically Something like this:

    http://example.com/issue1 --&gt; http://example.com/shop/issues/custom_issue_name1
    http://example.com/issue2 --&gt; http://example.com/shop/issues/custom_issue_name2
    http://example.com/issue3 --&gt; http://example.com/shop/issues/custom_issue_name3

Thanks!

How to redirect single URL in Nginx?

How do I remove the &lt;code&gt;&quot;index.php&quot;&lt;/code&gt; sticking out in every path in codeigniter somewhere in the center?
I want clean non &lt;code&gt;index.php-fied URLs&lt;/code&gt;?

How to remove &quot;index.php&quot; in codeigniter&#39;s path

I would like to redirect `www.example.com` to `example.com`. The following htaccess code makes this happen:

    RewriteCond %{HTTP_HOST} ^www\.example\.com [NC]
    RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

But, is there a way to do this in a generic fashion without hardcoding the domain name?

Generic htaccess redirect www to non-www

I&#39;ve not been able to understand the purpose of {R:N}. Could anyone please clarify when to use  
`{R:0}` vs. `{R:1}`

usage example:

&lt;!-- language: lang-xml --&gt;

    &lt;action type=&quot;Redirect&quot; url=&quot;http://www.{HTTP_HOST}/{R:0}&quot; /&gt;

I&#39;ve seen ScottGu using {R:1}

http://weblogs.asp.net/scottgu/archive/2010/04/20/tip-trick-fix-common-seo-problems-using-the-url-rewrite-extension.aspx


Whereas, below has {R:0}

http://weblogs.asp.net/owscott/archive/2009/11/27/iis-url-rewrite-rewriting-non-www-to-www.aspx 

Had a look at the IIS link below but could not quite digest the definition below:

&gt; Back-references to condition patterns are identified by {C:N} where N is from 0 to 9; back-references to rule pattern are identified by {R:N} where N is from 0 to 9. Note that for both types of back-references, {R:0} and {C:0}, will contain the matched string


IIS URL Rewrite {R:N} clarification

Is it possible to use .htaccess to rewrite a sub domain to a directory?

Example:


- http://sub.domain.com/ 

shows the content of 

- http://domain.com/subdomains/sub/

.htaccess rewrite subdomain to directory

**About the system**

I have URLs of this format in my project:-

    http://project_name/browse_by_exam/type/tutor_search/keyword/class/new_search/1/search_exam/0/search_subject/0

Where keyword/class pair means search with &quot;class&quot; keyword.

I have a common index.php file which executes for every module in the project. There is only a rewrite rule to remove the index.php from URL:-

    RewriteCond $1 !^(index\.php|resources|robots\.txt)
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ index.php [L,QSA]


I am using urlencode() while preparing the search URL and urldecode() while reading the search URL.

**Problem**

Only the forward slash character is breaking URLs causing 404 page not found error. 
For example, if I search `one/two` the URL is 

    http://project_name/browse_by_exam/type/tutor_search/keyword/one%2Ftwo/new_search/1/search_exam/0/search_subject/0/page_sort/

How do I fix this? I need to keep index.php hidden in the URL. Otherwise, if that was not needed, there would have been no problem with forward slash and I could have used this URL:-

    http://project_name/index.php?browse_by_exam/type/tutor_search/keyword/one
    %2Ftwo/new_search/1/search_exam/0/search_subject/0

urlencoded Forward slash is breaking URL

In my apache configuration I have the following simple rewrite rule which

1. unless file exists will rewrite to index.php
1. on the urls you never see the file extension (.php)

how can I rewrite this in nginx?


    #
    # Redirect all to index.php
    #
    RewriteEngine On

    # if a directory or a file exists, use it directly
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d

    RewriteCond %{REQUEST_URI} (/[^.]*|\.)$ [NC]
    RewriteRule .* index.php [L]

Here&#39;s how my nginx server block looks like now, but it doesn&#39;t work :(

    root /home/user/www;
    index index.php;

    # Make site accessible from http://localhost/
    server_name some-domain.dev;


    ###############################################################
    # exclude /favicon.ico from logs
    location = /favicon.ico {
        log_not_found off;
        access_log off;
    }   

    ##############################################################
    # Disable logging for robots.txt
    location = /robots.txt {
        allow all;
        log_not_found off;
        access_log off;
    }   

    ##############################################################
    # Deny all attempts to access hidden files such as 
    # .htaccess, .htpasswd, .DS_Store (Mac).
    location ~ /\. {
        deny all;
        access_log off;
        log_not_found off;
    }   

    ##############################################################
    #   
    location / { 
        include /etc/nginx/fastcgi_params;
        fastcgi_param   SCRIPT_FILENAME  $document_root/index.php$args;
        fastcgi_pass    127.0.0.1:9000;
    }   

    ###############################################################
    # serve static files directly
    location ~* ^.+.(jpg|jpeg|gif|css|png|js|ico)$ {
        access_log off;
        expires    30d;
    }   

    ###############################################################
    # redirect server error pages to the static page /50x.html
    error_page   500 502 503 504  /50x.html;
    location = /50x.html {
        root html;
    }   

    # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
    #   
    location ~ \.php$ {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        # NOTE: You should have &quot;cgi.fix_pathinfo = 0;&quot; in php.ini
        # With php5-cgi alone:
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_index index.php;
        include fastcgi_params;
    }

Rewrite all requests to index.php with nginx

For the site I am working on, we are in the process of improving our URLs for one type of resource - specifically, moving away from numerical IDs toward unique, descriptive strings. A similar example would be switching from identifying users by numerical database ID to identifying them by username (not our specific case, but analagous). So a URL to access a user&#39;s information used to look like:

    /users/48573

And now it looks like

    /users/thisisausername.

The only problem is that we still need to be able to fetch them through numerical IDs somehow, for legacy consumers of the API. We don&#39;t need the REST URLs themselves to redirect (e.g. `/users/48573` should not redirect to `/users/thisisausername`), we just need a method to obtain the right data using the old identifier. The solution should either provide an alternate way of accessing the user information (which conveniently includes the new identifier, username) by ID, or of accessing just the username by ID. Some possible solutions might be:

* Using a node to specify some alternate method of identification, e.g. `/users/byid/48573`
* Using a query parameter to specify some alternate method of identification, e.g. `/users/48573?fetchby=id` or `/users/48573?byid=true`
* Treating username-by-id as another resource, e.g. `/identifiers/username/48573`

Which of these (if any) is closest to proper REST? How would you deal with the problem?


REST - supporting multiple possible identifiers

When should a trailing slash be used in a URL? For example - should my URL look like `/about-us/` or like `/about-us`?
 
I am fully aware of the SEO-related issues - duplicate content and the canonical thing; I&#39;m trying to figure out which one I should use in the context of serving pages _correctly_ alone.

For example, my colleague is thinking that a trailing slash at the end means it&#39;s a &quot;folder&quot; - a &quot;directory&quot;, so this is not a correct style. But I think that without a slash in the end - it&#39;s not quite correct either, because it almost looks like a folder, but it isn&#39;t and it&#39;s not a normal file either, but a filename without extension.

Is there a proper way of knowing which to use?

When should I use a trailing slash in my URL?

I am designing a website. I want my website address to look like the following image:

![File name extensions like (PHP/JSP) are hidden][1]

I don&#39;t want my website to look like `http://something.com/profile.php`.
I want the `.php` extension to be removed in the address bar when someone opens my website. In other words, I want my website to be like: http://something.com/profile

As a second example, you can look at the Stack&amp;nbsp;Overflow website address itself.

How can I get this done?

  [1]: http://i.stack.imgur.com/fFFK1.png



How can I remove file extension from a website address?

I need the Url Rewrite module on my IIS But it does not install and says that I need at least IIS7




Url rewrite does not install on windows 10 IIS 10

I don&#39;t understand anything about IIS, but am trying to solve this problem of redirecting all visitors to domain.com/page to domain.com/page.html

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot; ?&gt;
    &lt;configuration&gt;
      &lt;system.webServer&gt;
        &lt;rewrite&gt;
              &lt;rewriteMaps&gt;
                  &lt;rewriteMap name=&quot;StaticRedirects&quot;&gt;
                      &lt;add key=&quot;/page&quot; value=&quot;/page.html&quot; /&gt;
                  &lt;/rewriteMap&gt;
                &lt;/rewriteMaps&gt;
          &lt;/rewrite&gt;
      &lt;/system.webServer&gt;
    &lt;/configuration&gt;

A couple of problems arise:

1. I don&#39;t know where to even put the file. There is a User root directory, and an htdocs directory, I tried both, no joy.
2. I don&#39;t even know if the account can do rewrites, I am trying to find that out.






All Url Rewriting Solutions on Gang of Coders

Total of 25 Url Rewriting Solutions

Apache: edit to .conf file produces "Invalid command 'Header'"