.htaccess file to index.php file doesn't work

I am trying to configure lilrul a open source url shortening device onto a ubuntu 8.10 intrepid lamp stack.

I have successfully installed the database using a combination of heidi, and phpmyadmin
However on the original install I did not use the .htaccess file to get the url to point to the index.php, and I am encountering strange errors.  When I input a long url, and have it shortened I receive no errors however the link is broken.

Trying the install on a fresh server image as of now I'm looking to try and use a .htaccess file to direct the webserver as per the instructions however, I have no idea if the .htaccess file is working or where to place it.

Not sure where to look at this point.
lilURL 0.1.1 http://lilurl.sourceforge.net
lilURL is a simple PHP/MySQL app that works basically like tinyurl.com,
allowing you to create shortcuts on your own server.
To install:
1. Create a MySQL database and user for lilURL.
2. Import the lilurl.sql file:
      (( like so:
         mysql -u <lilurl_user> -p <lilurl_db> < lilurl.sql
3. Edit the configuration file includes/conf.php to suit your needs.
4. Set up mod_rewrite, if necessary
      (( a .htaccess file with the lines:
         RewriteEngine On
         RewriteRule (.*) index.php
        should suffice ))
5. Buy 15 donuts and eat them all in one sitting.
Those are the setup instructions for lilurl
Below is my /etc/lilurl/includes/conf.php file
<?php /* conf.php ( config file ) */
// page title
define('PAGE_TITLE', 'lil&#180; URL Generator');
// MySQL connection info
define('MYSQL_USER', 'dabney');
define('MYSQL_PASS', 'coleman');
define('MYSQL_DB', 'lilurl');
define('MYSQL_HOST', 'localhost');
// MySQL tables
define('URL_TABLE', 'lil_urls');
// use mod_rewrite?
define('REWRITE', true);
// allow urls that begin with these strings
$allowed_protocols = array('http:', 'https:', 'mailto:');
// uncomment the line below to skip the protocol check
// $allowed_procotols = array();

Open in new window

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The .htaccess file needs to go in to the sites root directory, normally pointed to by DocumentRoot.

In the Directory settings for the site you also need to allow overrides.
IllyankeshAuthor Commented:
so that would be /var/www?  since it is just the simple 'it works!' default html script at the moment.  

As for The allowing overrides that should be set to on.  That would be in the apache.conf?
that is the snippet from the apache.conf  should the Deny from all say Allow?  The wording is confusing and makes it sound like I still want that denied?
AccessFileName .htaccess
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<Files ~ "^\.ht">
    Order allow,deny
    Deny from all

Open in new window

If your DocumentRoot is /var/www, then that is where the .htaccess file shouldgo.

No,  the "Deny from all" should stay that way.

What the does is exactly what the comment says, it prevent me from entering:




and pulling up your .htaccess file or your .htpasswd file.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

IllyankeshAuthor Commented:
So still not working, even with the .htaccess file in the /var/www directory.
The link below fixes the webpage of the lilurl, but I suspect is behind the other problems.

ln -s /etc/lilurl/index.php /var/www/index.php
In the:

<Directory />


Do you have:

     AllowOverride All

or any other AllowOverride?
IllyankeshAuthor Commented:
Don't think so what file would that be in?  I just have a standard LAMP stack on ubuntu, I'm not using any funky gui's to manage this.
Would that be /var/www ?
or is that the /etc/apache2/apache.conf?

I have not use Ubuntu, but I think it should be in apache.conf
IllyankeshAuthor Commented:
Ooooo that is progress now ...after adding AllowOverride All into the apache.conf file I get the below error.
So perhaps my .htaccess file is not written correctly?

Failed to Connect
Firefox can't establish a connection to the server at
Though the site seems valid, the browser was unable to establish a connection.
    * Could the site be temporarily unavailable? Try again later.
    * Are you unable to browse other sites?  Check the computer's network connection.
    * Is your computer or network protected by a firewall or proxy? Incorrect settings can interfere with Web browsing.
RewriteEngine On
RewriteRule (.*) /index.php
should the /index.php  have the full path to the file I'm assuming?

Open in new window

IllyankeshAuthor Commented:
Nope nevermind that was my bad I got a

 * Restarting web server apache2                                                                                 Syntax error on line 38 of /etc/apache2/apache2.conf:
AllowOverride not allowed here

when adding the AllowOverride bit to the file
IllyankeshAuthor Commented:
Uncommented a large string of stuff at the end of the apache.conf file including one that that said AllowOverride None, and changed that to AllowOverride All

Now I get this error.

The requested URL was not found on this server.  The link on the ">referring page seems to be wrong or outdated. Please inform the author of ">that page  about the error.  If you entered the URL manually please check your spelling and try again.

IllyankeshAuthor Commented:
which is weird since apache is running, and when I chop off the /index.php  I get the default it works page
...any ideas?
Rename the .htaccess file and see if the site works.
IllyankeshAuthor Commented:
Rename it to what?  .htaccess I'm assuming?
Anything.  The idea is NOT to use it and see if the basics of Apache is working.

Once you verify the basics are working, then rename it back to .htaccess.

If everything is working, when you enter:


the .htaccess file will redirect you to:


If you enter:


it will re-direct you to:


IllyankeshAuthor Commented:
ok, set apache.conf back to default, and renamed .htaccess file.

I get
Not Found

The requested URL /index.php was not found on this server.
Apache/2.2.9 (Ubuntu) PHP/5.2.6-2ubuntu4.2 with Suhosin-Patch Server at Port 80

when attempting to go to http://myurl/index.php

When I go to http://myurl
I get the default
It Works!  apache standard welcom page

IllyankeshAuthor Commented:
There was an extra Directory section in the sites-available/default file.  I made a couple of other minor changes, but it was a very difficult problem to diagnose, because it just kept looking like we had the wrong regular expression in the mod_rewrite line.  So, I kept trying pretty much every permutation of the the regex I could think of with no impact.  Deleting the extra Directory section cleared up the whole problem, and the regex that came with the lilurl distro worked like a charm.

This cleared up the overall problem on the main server... still have no idea why the .htaccess was not working.
If you entered:


and got a 404 not found, that means that in your DocumentRoot (/var/www) you did not have the file "index.php".  Please note, if you are not familiar with Linux, file names are case sensitive, so index.php is not the same as INDEX.PHP, or even Index.PHP.
IllyankeshAuthor Commented:
Right.  The index.php file is in /etc/lilurl  which is why I needed the .htaccess redirect to get people there.
I had the .htaccess in the /var/www/ and was still not working.  though I did get some of the weirder errors last night, when I began playing with some of the /etc/apache2/apache.conf files.  Which are listed above.

Renaming the .htaccess file brought me the 404 error again...which was what I was getting last night after I only commented out some of the error files at the bottom of the apache.conf file.

All files referenced by a URL must be in a directory that is defined in Apache by a <Directory></Directory> stanza.

If you had the .htaccess to just redirect http://myurl to http://myurl/index.php, the better way to do that is to get rid of the .htaccess and then in your apache.conf file change:

     DirectoryIndex index.html


     DirectoryIndex index.php

This will make the default page index.php.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IllyankeshAuthor Commented:
Thanks man, was a combination of my newbness, and some strange errors which took my chief engineer the greater part of last night to figure out.
The softlink solution worked over the .htaccess file.  I was trying to get the .htaccess file solution to work in an effort to troubleshoot the greater error that was involved.  Which was infact an entire extra directory was being created by the index.php file.  Once that directory was removed, the rest of the script functioned as normal.
So the Softlink solution would infact also work as well as changing the default root directory.
Glad I could be of help.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.