1. In `httpd.conf` on `/Applications/MAMP/conf/apache`, find:

        &lt;Directory /&gt;
            Options Indexes FollowSymLinks
            AllowOverride None
        &lt;/Directory&gt;

2. Replace `None` with `All`.

3. Restart MAMP servers.

Go to `httpd.conf` on `/Applications/MAMP/conf/apache` and see if the `LoadModule rewrite_module modules/mod_rewrite.so` line is un-commented (without the # at the beginning)

and change these
 from   ...
 

	&lt;VirtualHost *:80&gt;
		ServerName ...
		DocumentRoot /....
	&lt;/VirtualHost&gt;

To this:

	&lt;VirtualHost *:80&gt;
		ServerAdmin ...
		ServerName ...
	
		DocumentRoot ...
		&lt;Directory ...&gt;
			Options FollowSymLinks
			AllowOverride None
		&lt;/Directory&gt;
		&lt;Directory ...&gt;
			Options Indexes FollowSymLinks MultiViews
			AllowOverride All
			Order allow,deny
			allow from all
		&lt;/Directory&gt;
	&lt;/VirtualHost&gt;


I&#39;m using MAMP (downloaded today) and had this problem also. The issue is with this version of the MAMP stack&#39;s default httpd.conf directive around line 370. Look at httpd.conf down at around line 370 and you will find:

	&lt;Directory &quot;/Applications/MAMP/bin/mamp&quot;&gt;
		Options Indexes MultiViews
		AllowOverride None
		Order allow,deny
		Allow from all
	&lt;/Directory&gt;

You need to change:     AllowOverride None
To:                     AllowOverride All



If you have MAMP PRO you can set up a host like mysite.local, then add some options from the &#39;Advanced&#39; panel in the main window. Just switch on the options &#39;Indexes&#39; and &#39;MultiViews&#39;. &#39;Includes&#39; and &#39;FollowSymLinks&#39; should already be checked.

The problem I was having with the rewrite is that some .htaccess files for Codeigniter, etc come with

    RewriteBase /

Which doesn&#39;t seem to work in MAMP...at least for me.

I want to format a string with `sprintf` but repeating many times an argument. see..

    $str = &quot;Str 1: %s - Str 2: %s - Str 2 again: %s&quot;;

Considering that string to format, I want to repeat the second arg two times.

    echo sprintf($str, &quot;I&#39;m string 1&quot;, &quot;My name is string 2&quot;);

And the wanted result like: 

    Str 1: I&#39;m string 1 - Str 2: My name is string 2 - Str 2 again: My name is string 2

There&#39;s a way to do that??

sprintf - repeating arguments

&gt; **Possible Duplicate:**  
&gt; [How to use nodejs to open default browser and navigate to a specific URL](https://stackoverflow.com/questions/8500326/how-to-use-nodejs-to-open-default-browser-and-navigate-to-a-specific-url)  

&lt;!-- End of automatically inserted text --&gt;

I don&#39;t know if it matters, but I am on OSX.

I know you can launch a browser from the command line itself by typing:

    open http://www.stackoverflow.com

But is there a way to open a browser from inside a nodejs command line script?

How would you launch a browser from the a node.js command line script

I am trying to get the `.htaccess` working in MAMP.

The content of the `.htaccess` is a simple redirect line but it does not work. I am trying to manipulate URLs of a WordPress page, so I added the `.htaccess` file in my theme folder, but it is not working.

Is there any settings within MAMP i need to change to get the `.htaccess` file to work?



How to get htaccess to work on MAMP

I am trying to get the <code>.htaccess</code> working in MAMP.
The content of the <code>.htaccess</code> is a simple redirect line but it does not work. I am trying to manipulate URLs of a WordPress page, so I added the <code>.htaccess</code> file in my theme folder, but it is not working.
Is there any settings within MAMP i need to change to get the <code>.htaccess</code> file to work?

I have added `set_time_limit(0);` function to increase execution time but its executing only 2-3 minutes maximum.

```php
error_reporting(E_ALL);
error_reporting(1);
set_time_limit(0);
```

I want to search links from a site which is taking a long time.

Increase max execution time for php

For my site I have the following htaccess rules:

    # BEGIN Gzip
    &lt;IfModule mod_deflate.c&gt;
    AddOutputFilterByType DEFLATE text/text text/html text/plain text/xml text/css application/x-javascript application/javascript
    &lt;/IfModule&gt;
    # END Gzip
    
    # BEGIN EXPIRES
    &lt;IfModule mod_expires.c&gt;
        ExpiresActive On
        ExpiresDefault &quot;access plus 10 days&quot;
        ExpiresByType text/css &quot;access plus 1 month&quot;
        ExpiresByType text/plain &quot;access plus 1 month&quot;
        ExpiresByType image/gif &quot;access plus 1 month&quot;
        ExpiresByType image/png &quot;access plus 1 month&quot;
        ExpiresByType image/jpeg &quot;access plus 1 month&quot;
        ExpiresByType application/x-javascript &quot;access plus 1 month&quot;
        ExpiresByType application/javascript &quot;access plus 1 month&quot;
        ExpiresByType application/x-icon &quot;access plus 1 year&quot;
    &lt;/IfModule&gt;
    # END EXPIRES

I&#39;ve just updated my site and it looked all screwy until I cleared my cache. How can I force the client&#39;s browser to clear the cache after an update so that the user can see the changes?

htaccess - How to force the client&#39;s browser to clear the cache?

I&#39;ve been cleaning up my project lately. I have a main .htaccess in the root directory and 6 others. 5 of them ran `Options -Indexes` which i didn&#39;t see anypoint of allowing any Directory viewing so moved that to the main one. so now i only have 2 .htaccess files. the main and one in `/system` which holds

    # Block External Access
    deny from all

So i wanted to run that on `/system` only from within the main. So i deleted the one in /system and added

     # Block External Access
    &lt;Directory &quot;/system/&quot;&gt;
    deny from all
    &lt;/Directory&gt;

 to my main .htaccess file leaving 1! 

but now i get a 

&gt; Internal Server Error
&gt; 
&gt; The server encountered an internal error or misconfiguration and was
&gt; unable to complete your request.
&gt; 
&gt; Please contact the server administrator, webmaster@localhost and
&gt; inform them of the time the error occurred, and anything you might
&gt; have done that may have caused the error.
&gt; 
&gt; More information about this error may be available in the server error
&gt; log.
&gt; 
&gt; Apache/2.2.17 (Ubuntu) Server at 10.0.1.5 Port 80

The goal is to block reading any files in /system and it&#39;s sub directory&#39;s but allow viewing of everything else all from one `.htaccess` file for the whole project. Any ideas on how i can fix this? I did some Google searches but couldn&#39;t really come out with anything.

htaccess &lt;Directory&gt; deny from all

I need to exclude one Url (or even better one prefix) from normal htaccess Basic Auth protection. Something like `/callbacks/myBank` or `/callbacks/.*`
Do you have any hints how to do it?

What I&#39;m not looking for is how to exclude a file. 
This has to be url (as this is solution based on PHP framework, and all urls are redirected with `mod_rewrite` to `index.php`). So there is no file under this URL. Nothing.

Some of those urls are just callbacks from other services (No IP is not known so I cannot exclude based on IP) and they cannot prompt for User / Password.

Current definition is as simple as:

```bash
AuthName &quot;Please login.&quot;
AuthGroupFile /dev/null
AuthType Basic
AuthUserFile /xxx/.htpasswd
require valid-user 
```

htaccess exclude one url from Basic Auth

Many posters have problems debugging their RewriteRule and RewriteCond statements within their **`.htaccess`** files.  Most of these are using a shared hosting service and therefore don&#39;t have access to the root server configuration. They cannot avoid using `.htaccess` files for rewriting and _cannot_ enable a RewriteLogLevel&quot; as many respondents suggest.  Also there are many `.htaccess`-specific pitfalls and constraints are aren&#39;t covered well.  Setting up a local test LAMP stack involves too much of a learning curve for most.   

So my Q here is how would we recommend that they ***debug*** their rules _themselves_.  I provide a few suggestions below.  Other suggestions would be appreciated.

 1. **Understand that the mod_rewrite engine cycles through `.htaccess` files**. The engine runs this loop:

        do
          execute server and vhost rewrites (in the Apache Virtual Host Config)
          find the lowest &quot;Per Dir&quot; .htaccess file on the file path with rewrites enabled
          if found(.htaccess)
             execute .htaccess rewrites (in the user&#39;s directory)
        while rewrite occurred

    So your rules will get executed repeatedly and if you change the URI path then it may end up executing other `.htaccess`files if they exist. So make sure that you terminate this loop, if necessary by adding extra `RewriteCond` to stop rules firing.  Also delete any lower level `.htaccess` rewrite rulesets unless explicitly intent to use multi-level rulesets.  

 2. **Make sure that the syntax of each Regexp is correct** by testing against a set of test patterns to make sure that is a valid syntax and does what you intend with a fully range of test URIs.  See [answer below][1] for more details.

 3. **Build up your rules incrementally in a test directory.**  You can make use of the &quot;execute the deepest `.htaccess` file on the path feature&quot; to set up a separate test directory (tree) and debug rulesets here without screwing up your main rules and stopping your site working.  You have to add them one at a time because this is the only way to localise failures to individual rules.

 4. **Use a dummy script stub to dump out server and environment variables**. (See **Listing 2**)If your app uses, say, `blog/index.php` then you can copy this into `test/blog/index.php` and use it to test out your blog rules in the `test` subdirectory.  You can also use environment variables to make sure that the rewrite engine in interpreting substitution strings correctly, e.g.

        RewriteRule ^(.*) - [E=TEST0:%{DOCUMENT_ROOT}/blog/html_cache/$1.html]

    and look for these **REDIRECT_\*** variables in the phpinfo dump.  BTW, I used this one and discovered on my site that I had to use `%{ENV:DOCUMENT_ROOT_REAL}` instead.  In the case of redirector looping  **REDIRECT_REDIRECT_\*** variables list the previous pass. Etc.. 

 5. **Make sure that you don&#39;t get bitten by your browser caching incorrect 301 redirects**.  See [answer below][2].  My thanks to [Ulrich Palha][3] for this.

 6. The rewrite engine seems sensitive to cascaded rules within an `.htaccess` context, (that is where a `RewriteRule` results in a substitution and this falls though to further rules), as I found bugs with internal sub-requests [(1)][4], and incorrect **PATH_INFO** processing which can often be prevents by use of the \[NS\], \[L\] and \[PT\] flags.

Any more comment or suggestions?

## Listing 1 -- phpinfo ##

    &lt;?php phpinfo(INFO_ENVIRONMENT|INFO_VARIABLES);

  [1]: https://stackoverflow.com/questions/9153262/tips-for-debugging-htaccess-rewrite-rules/9261963#9261963
  [2]: https://stackoverflow.com/questions/9153262/tips-for-debugging-htaccess-rewrite-rules/9261963#9204355 
  [3]: https://stackoverflow.com/users/499472/ulrich-palha
  [4]: http://httpd.apache.org/docs/2.2/rewrite/flags.html#flag_n

Tips for debugging .htaccess rewrite rules

I am developing a single page Javascript application in MAMP. My JavaScript and HTML template files are getting cached between requests.

Is there a simple way to indicate in MAMP that I want to prevent http file caching? Possibly with a `.htaccess` file? Where do I place the `.htaccess` or modify the virtual host for MAMP on Mac?

How to prevent http file caching in Apache httpd (MAMP)

I have recently got a mac an am not used to developing on a mac at all.

I have MAMP Pro 1.9.6.1. I did a locate on `php.ini` and got this:

    $ locate php.ini
    /Applications/MAMP/conf/php5.2/php.ini
    /Applications/MAMP/conf/php5.3/php.ini
    /Library/Application Support/appsolute/MAMP PRO/conf/php.ini
    /private/etc/php.ini.default

I changed the name of all of them. Restarted MAMP. It loaded without a hitch (I know odd right?). I am using PHP version 5.2.

All of these files are now different names (done one by one for process of elimination).
So I figure restart the mac. Same, MAMP loaded no problems, even though all of the `php.ini` files had been move. On Lamp this that wouldn&#39;t even load. But either there is another `php.ini` file I&#39;m missing (quite possible I don&#39;t know how to `updatedb`), MAMP is really intelligent and just pulls in all of them (less likely) or it doesn&#39;t use one.

Where does MAMP keep its php.ini?

I&#39;ve had MAMP working for a few months and recently installed PostgreSQL.  It recommended installing Apache as well, which I did to make sure PostgreSQL worked.  I then uninstalled PostgreSQL and the apache build and tried to restart MAMP.  It fired up the MySQL database (green light) but Apache didn&#39;t start.  I uninstalled and reinstalled MAMP only to face the same problem.

Apache doesn&#39;t seem to be logging any errors in the MAMP folder, so without any errors to report I&#39;m struggling with where to begin fixing it.  I&#39;m hoping its to do with the fact that I installed another version (and deleted it) that has caused the problem but I&#39;m too inexperienced to know what I&#39;ve done.

Where might I find any errors if not in the MAMP folder? Not in:

- /Applications/MAMP/Library/logs
- /Applications/MAMP/bin/logs



Apache not starting in MAMP (but MySQL working) in OSX

OK this is getting very frustrating. MAMP used to display errors but then stopped. I decided to do a fresh install of it as I couldn&#39;t figure it out. I check my PHP version, running 5.4.4 and go to that folder and change the php.ini to this:

    error_reporting  =  E_ALL
    display_errors = On

Still no errors showing. I go through all the folders and change all php.ini files, just in case. Nothing. I fix the forced error and dump out `phpinfo()`, check the error section and display_errors is Off. What the hell. 

I place `error_reporting(E_ALL); ini_set(&#39;display_errors&#39;, &#39;on&#39;);` at the start of the PHP file and `phpinfo()` again. Local value is now On, master is still Off. Force a PHP error, and still get Server Error not PHP error. 

Anybody have any insight? I have a bug somewhere in some code and cannot find it, would love for PHP to just tell me. 

Why MAMP doesn&#39;t display errors?

The current version of MAMP that I have only has php 5.2.17 and 5.4.4. I need 5.3.X. Is there a way to add additional versions that can be selected in the MAMP interfaces php preferences? This is for the free version of MAMP, not MAMP PRO.

Thanks

Content Type	Original Author	Original Content on Stackoverflow
Question	aurel	View Question on Stackoverflow
Solution 1 - .Htaccess	Emanuil Rusev	View Answer on Stackoverflow
Solution 2 - .Htaccess	salahy	View Answer on Stackoverflow
Solution 3 - .Htaccess	qommander	View Answer on Stackoverflow
Solution 4 - .Htaccess	strangerpixel	View Answer on Stackoverflow
Solution 5 - .Htaccess	SomethingOn	View Answer on Stackoverflow

How to get htaccess to work on MAMP

.Htaccess Problem Overview

.Htaccess Solutions

Solution 1 - .Htaccess

Solution 2 - .Htaccess

Solution 3 - .Htaccess

Solution 4 - .Htaccess

Solution 5 - .Htaccess

How would you launch a browser from the a node.js command line script

sprintf - repeating arguments

Attributions