Was trying to access my PHP web project from my Vista on my Ubunut and end up running error 403 Forbidden You don’t have permission to access on this server …
Well this has a very easy remedy:
BTW – I am using Uniserver – http://www.uniformserver.com/ – [ By the way it is the coolest development environment on windows as you would get PHP, MySQL, and PhpMyAdmin residing all at one place. But it doesn't matter if you are using other tool.
1. Go to where your www folder
2. open .htaccess file using your favorite text editor - note pad is more than enough for this.
3. Under Allow From 127.0.0.1 - or whatever it is allowed Add Allow From [your ip address of the computer from which you want to access the server]

A walk in the park!

เวลาเอา web app ที่เขียนด้วย cakephp ไปใส่ใน userdir เช่น /home/veer/public_html/myapp (ซึ่งมักจะไปตรงกับ url http://hostname/~veer/myapp) มักจะมีปัญหากับ mod_rewrite ขึ้นมา แต่ก็แก้ไม่ยาก เพียงแต่แก้ .htaccess ใน myapp กับ myapp/app/webroot

เดิมทีจะเขียนไว้ประมาณนี้ (ใน myapp กับ myapp/app/webroot ไม่เหมือนกัน แต่ก็แก้เหมือนกัน)

   RewriteEngine on
   RewriteRule    ^$ app/webroot/    [L]
   RewriteRule    (.*) app/webroot/$1 [L]

ก็แก้โดยใส่ RewriteBase เข้าไปเป็นแบบนี้

   RewriteEngine on
   RewriteBase    /~veer/myapp
   RewriteRule    ^$ app/webroot/    [L]
   RewriteRule    (.*) app/webroot/$1 [L]

เสร็จแล้ว

You can stop the hotlinking from outsider domain by using following rule in .htaccess

RewriteEngine On
RewriteCond %{HTTP_REFERER} ^http://(.+.)?domain.com/ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http://(.+.)?domain1.com/ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http://(.+.)?domain2.com/ [NC]
RewriteRule .*.(jpe?g|gif|bmp|png)$ /images/nohotlink.jpe [L]

You can also display a 403 Forbidden Error page instead of an image (nohotlink.jpe)

Replace last line on above code with the following code

RewriteRule .*.(jpe?g|gif|bmp|png)$ – [F]

If you were to change your website to a new domain or changed the location of an existing file, and you have your url indexed by search engines. If the pages are redirected you could end up loosing a lot of traffic by users getting the 404 error.

You can sort those by using redirection. This can be achieved by http-equiv, javascript or by using some server side code. But the simplest way is by using .htaccess 301 redirect.

This method is search engine friendly and is the easiest way around.

Just add the following code to your .htaccess file placed in your old site.

Redirect 301 /olddirectory/oldfile.html http://yoursite.com/newdirectory/newfile.html

redirect 301 (the instruction that the page has moved)

/old/old.htm (the original folder path and file name)

http://www.yoursite.com/newdirectory/newdirectory/newfile.html (new path and file name)

Test  immediately after implementing 301 redirects. If you find anything wrong, remove the redirect immediately.

Preventing directory listings can be very useful if for example, you have a directory containing important ‘.zip’ archive files or to prevent viewing of your image directories. Alternatively it can also be useful to enable directory listings if they are not available on your server, for example if you wish to display directory listings of your important ‘.zip’ files.

To prevent directory listings, create a .htaccess file following the main instructions and guidance which includes the following text:

IndexIgnore *

The above lines tell the Apache Web Server to prevent directory listings of directories and files within the directory containing the .htaccess file. The ‘*’ represents a wildcard, this means it will not display any files. It is possible to prevent listings of only certain file types, so for example you can show listings of ‘.html’ files but not your ‘.zip’ files.

To prevent listing ‘.zip’ files, create a .htaccess file following the main instructions and guidance which includes the following text:

IndexIgnore *.zip

The above line tells the Apache Web Server to list all files except those that end with ‘.zip’.

To prevent listing multiple file types, create a .htaccess file following the main instructions and guidance which includes the following text:

IndexIgnore *.zip *.jpg *.gif

The above line tells the Apache Web Server to list all files except those that end with ‘.zip’, ‘.jpg’ or ‘.gif’.

Alternatively, if your server does not allow directory listings and you would like to enable them, create a .htaccess file following the main instructions and guidance which includes the following text:

Options +Indexes

The above line tells the Apache Web Server to enable directory listing within the directory containing this .htaccess file. You can also reverse this to disable directory listings by replacing the plus sign before the text ‘Indexes’ with a minus sign. e.g. ‘Options -Indexes‘.

Hoy en día, somos muchos los desarrolladores que disfrutamos de las bondades de este muy buen framework, pero siempre se ha tenido el problema para quitar esa porcion de url “index.php” de nuestros proyectos.

Bien, pues luego de investigar, buscar y preguntar… y demas cosas, encontre un modo de retirar ese “index.php”, el cual lo trabaje en una distro de Linux.

Pues comencemos:

• Como sabran, se necesita activar el mod_rewrite en la configuracion de nuestro servidor Apache. Pues se puede hacer manualmente accediendo al archivo de configuracion o simplemente ejecutando el siguiente comando:   sudo a2enmod rewrite
• Una vez activado el mod_rewrite, procederemos a quitar las restricciones en el archivo:  sudo gedit /etc/apache2/site-enable/000-default , donde reemplazaremos todos los “AllowOverride None” por “AllowOverride All“.
• Una vez terminado esto, procedemos a reiniciar el servicio de Apache con: sudo /etc/init.d/apache2 restart .
• Si al reiniciar el servicio de Apache, por casualidad les aparece mensaje como: apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName , no se preocupen, se soluciona agregando la siguiente linea: ServerName localhost en el apache2.conf.
• Es hora de comprobar que en nuestro archivo de configuracion  ”system/application/config/config.php” , esté ya modificado la opcion del index page, de modo que quede así:  $config['index_page'] = “”;
• Ahora viene lo más importante, y es crear un archivo: .htaccess con el siguiente contenido, en la carpeta donde se encuentra nuestro proyecto, es decir donde se encuentra la carpeta “system”:

        ErrorDocument 404 /index.php

        DirectoryIndex index.php.

        <IfModule mod_rewrite.c>
        RewriteEngine on
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^(.*)$ index.php/$1 [L,QSA]
        </IfModule>

Y con esto ya tenemos podemos trabajar sin el poco querido: index.php , es decir, si nuestra url era: http://localhost/proyecto/index.php/controlador ahora sera simplemente http://localhost/proyecto/controlador.

Espero les haya servido este post, ya saben que cualquier consulta, pueden hacerla dejandonos un comentario, y nosotros gustosamente responderemos. Gracias.

Pada tutorial ini, akan menggunakan directory test1 dan test2.

1 Membuat directory

- cd /var/www/html
- mkdir test1
- mkdir test2

2. Membuat file HTML di masing-masing directory

- vi /var/www/html/test1/index.html
- vi /var/www/html/test2/index.html

3. Browsing ke masing-masing Halaman test.

Silakan menggunakan browser untuk browsing ke masing-masing halaman, yaitu http://localhost/test1 dan http://localhost/test2

Anda akan berhasi melihat isi dari masing-masing index.html yang ada.

4. Pembuatan file .htaccess

- cd /var/www/html/test1
- vi .htaccess

Isi file .htaccess adalah sbb :

Berikut penjelasan parameter-parameter yang ada :

- AuthName : judul dari pop yang muncul.
- AuthType
- Basic
- AuthUserFile : lokasi file .htpassword, berisi password dari user yang diperbolehkan login
- require user

Selanjutnya silakan copy file .htaccess tersebut ke /var/www/html/test2 dengan command : cp /var/www/html/test1/.htaccess /var/www/html/test2/

5. Create user
adduser testuser
passwd testuser

6. Menginfokan apache ttg user tersebut
htpasswd -c /etc/httpd/conf/.htpasswd testuser

7. Edit file httpd.conf

8. Restart service apache
service httpd restart

9. Testing
Selanjutnya silakan browsing lagi halaman http://localhost/test1 dan http://localhost/test2

Referensi :

- http://www.howtoforge.com/htaccess_authentication

Problem Description:

Previously I had tried migrating an existing customer database from Xcart 3.5 to Magento. I was successful at exporting the database from Xcart, but, I was unsuccessful at importing all of the customer records into Magento. The import tool relies upon AJAX to accomplish the customer and product importing. I determined that Magento did not finish importing the customers because the PHP session was timing out. I tried setting the session within the Magento administrative interface. I set the session time to 86400 seconds (or 24 hours). This did not fix my problem.

Solution

I altered the main .htaccess file. I appended the following lines to the bottom of the file.

php_value session.cookie_lifetime 86400
php_value session.gc_maxlifetime 86400

Typically a PHP session will timeout after 24 minutes. I recommend altering your htaccess file only temporarily. By having a very long PHP session max life time for your PHP session you increase the chances of someone hacking your web site by using a technique called session fixation a method of session highjacking.

After you are done make sure to change the session time out value within the Magento adminstrative interface and remove the above lines from the htaccess file.

<![CDATA[If you want to redirect your .htm pages to .php pagesand you've got mod_rewrite enabled on your server you can put this in your .htaccess file:### h

En las últimas horas se han descubierto algunos problemas de seguridad en Joomla!. Se trata de fallas que permite descubrir versiones de ciertos módulos y que permite a usuarios maliciosos a manipular ciertos datos.

En concreto se trata de un error en el manejo de archivos XML que puede ser explotado para ver la versión de los módulos instalados. Además un error no especificado en la solicitud de datos puede ser explotado para modificar artículos de la página principal de otros usuarios.

Los problemas de seguridad se presentan en versiones anteriores a la 1.5.15.

SOLUCIÓN: Actualizar a la versión 1.5.15 y restringir el acceso a los archivos XML (por ejemplo, a través de un “. Htaccess”).

A quick tutorial showing how to remove “.html” suffix from the url of your website 

1. Go to “Settings” (it’s under “System” section), make sure to set:

• URL suffix: empty the field
• Rewrite URLs: checked
• Disable page alias usage: unchecked

Open the “.htaccess”  (it is located into the root of your website) and replace the line containing

RewriteRule .*\.html$ index.php [L]

with:

RewriteRule .* index.php [L]

That’s all.

Para você que possue os recursos disponíveis em seu servidor de hospedagem em PHP e que criou suas páginas com um conteudo estático e que agora quer deixá-las dinâmicas e com diversos recursos que só o PHP pode lhe oferecer?.

Não pense que é apenas renomear os arquivo para a extensão php os seus arquivos com extensão .htm ou .html. Mas o processo é muito simples:

Salve .htaccess! O arquivo modificador de configurações do Apache, válido e ativo na maioria dos servidores web. A dica é fazer o servidor tratar os arquivos de extensão “.html” ou “.htm” como se fossem páginas PHP, ou seja, processando os scripts deles.

Crie um arquivo de texto em branco, e digite (ou cole) estas duas linhas:

AddType application/x-httpd-php htm
AddType application/x-httpd-php html

Salve-o com o nome “.htaccess” na pasta raiz do seu site, e publique-o. É só isso!

Cuidado com o nome do arquivo, caso você nunca tenha usado. Ele começa com um ponto e não tem extensão. No Linux/Unix ficará oculto, devido começar com um ponto. Para exibi-lo no seu gerenciador de arquivos local, por exemplo, pode ser necessário pedir para mostrar os arquivos ocultos.

Uma vez dentro da pasta raiz, ele vale para a pasta atual e para todas as subpastas.

Se você já usou o .htaccess alguma vez e já tem ele configurado, então não crie um novo: edite o antigo, adicionando estas duas linhas nele.

Fazer isso “transformará” suas páginas HTML em páginas PHP sem precisar renomear os arquivos.

Tecnicamente você poderia usar a extensão que quiser, eu por exemplo, uso a extensão .i9se (arquivo.i9se). Mas alguns servidores não registram corretamente o tipo mime ao usar uma extensão diferente, e alguns navegadores podem acabar por mostrar o código-fonte da página, em vez do conteúdo HTML renderizado.

Se seu servidor não reconhecer o .htaccess, pode ser necessário configurar o Apache manualmente (caso você tenha acesso à administração do servidor) ou entrar em contato com o suporte, nos planos de hospedagem compartilhada (que vem a ser o caso da maioria). Mas como sempre, antes de entrar em contato com o suporte, certifique-se de que o arquivo .htaccess esteja salvo corretamente na pasta do seu site.

Fonte: Código Fonte

I have changed the links of the .htaccess root file of the Wigbi Demos.

Previously, the file definied the links relative to the server root (/wigbi_demos/…) but not they are relative to the application root folder.

This means that you do not have to adjust this file when you download the new version of the Wigbi Demos.

Para bloquear imagens, vídeos ou outros arquivos quaisquer de seu site para que outras pessoas não as utilize sem a sua autorização, é muito simples, Veja como:

• Crie um arquivo chamado .htaccess (exatamente assim, com um ponto na frente). Normalmente ele já deverá estar criado na pasta raiz de seu site.
• Coloque neste arquivo o conteúdo de texto abaixo:

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http://(www.)?seudominio.com/.*$ [NC]
RewriteRule .(gif|jpg|png|js|css)$ - [F]
</IfModule>

Substitua seudominio.com pelo endereço do seu site. No exemplo está sendo bloqueado o acesso a qualquer imagem . GIF, .JPG , .JS e . CSS.

Para adicionar outros formatos basta editar o campo (gif|jpg|png|js|css) separando cada nome com uma barra |.

Você pode bloquear vídeos e músicas (.WMV, .MPEG, .MP3, .WAV etc). Pode bloquear também links para arquivos .PDF, .DOC, .TXT e qualquer outro formato que desejar.

Dessa forma somente o seu site terá permissão para ter links apontados para estes tipos de arquivo.

Fonte: Código Fonte

Hello, in this tutorial – I will show you how to create a custom error page for your site. In this tutorial – we will be focusing on the Error 404 page, which is displayed when the page can’t be found.

So, follow these steps:

1. Log in to your website control panel.
2. Create a new file.
3. In this file enter the following text: ErrorDocument 404 404.html
4. Save this file in your ROOT directory as: .htaccess
5. Now open your website editor.
6. Create a new HTML file, named: 404.html
7. Enter custom text, such as: Error 404 – The Page You Were Looking For Could Not Be Found.
8. Upload this also to your ROOT directory.

Now if you navigate to your website, and type a sub-direcotry you know dosen’t exist – your error 404 page should display – if not – you need to follow these steps again.

You can try this by going to my website, and adding a false directory onto the end of the url, e.g:

http://www.mytutorialz.isgreat.org/false-directory

Enjoy.

Tutorial Joomla Pemula kali ini akan membahas sebuah tema yaitu stensi Joomla Menjadi HTML dengan htaccess.

Pada sebuah web yang dibuat dengan joomla biasanya akan menampilkan sebuah rl kurang lebih sebagai berikut

http://www/domain.com/index.php?option=com_content&view=article&id=75&Itemid=70
api pernahkah anda menjumpai sebuah website atau blog yang dibuat dengan joomla menjadi berakhiran (berekstensi) HTML
http://www/domain.com/profil.html atau http://www.nama.net/galeri.html dan sebagainya…..
ternyata ekstensi url pada web bebasis Joomla dapat diubah menjadi berekstensi HTML hanya dngan sedikit langkahyang mudah yaitu :

pada file instalasi Joomla terdapat sebuah file bernama htacess dngan ekstensi txt atau htaccess.txt….
nah file inilah yang perlu sedikit kita sentuh (kaya apa aja disentuh) untuk dapat merubah url web Joomla menjadi berakhiran HTML… caranya……??

Kita harus merubah file htacess.txt tersebut menjadi file bernama .htacess
kurang lebih ada dua cara merubah file htaccess.txt tersebut menjadi file bernama .htaccess yaitu:

• dari komputer lokal… untuk pengguna windows sering menemui kesulitan dalam merubah nama (rename) sebuah file dengan awalan titik ( . ) di nama file tersebut.. namun hal ini tidak terjadi pada komputer dengan sistem operasi linux…. nah untuk pengguna windows dapat melakukan perubahan nama (rename) tersebut dengan command prompt
  yaitu ;
  ren htaccess.txt .htaccess
  setelah itu upload file tersebut ke direktori utama webstie anda
• dengan FTP…jalankan FTP anda , masuk ke htdocs atau public html
  (bisa berbeda untuk server hosing yang berbeda)… setealah daftar file muncul langsung saja rename file bernama htaccess.txt menjadi .htaccess ( tanpa ekstensi)

Selah salah satu langkah tadi selesai login ke halaman administrato website anda, pilih site – global configuration
pada sebuah kanan terdapat pilihan SEO setting dan terdapat tiga pilihan
Search Engine Friendly URLs
Use Apache mod_rewrite dan
Add suffix to URLs
setelah itu centang pada pilihan yes pada ketiga pilihan tersebut dan hasilnya dapat adan lihat pada url halaman web pada browser anda.

Demikian sedikit tutorial joomla pemula dari saya yang newbie juga ini …kalau ada kesalahan mohon pencerahannya…..

SEO Settings Search Engine Friendly URLs No Yes Use Apache mod_rewrite No Yes Add suffix to URLs No Yes

La configurazione del server web apache viene descritta da delle direttive inserite nei file di configurazione. Il file di configurazione principale è httpd.conf; ulteriori file di configurazione possono essere aggiunti utilizzando la direttiva Include.

Per esempio nelle installazioni di default di ubuntu il file httpd.conf è vuoto, mentre partecipano alla configurazione del server web i file:

• apache2.conf

• ports.conf

• tutti i file all’interno di sites-enabled (Virtual host abilitati)

Per testare la corretta sintassi di tutti i file di configurazione che partecipano alla personalizzazione del servizio apache è sufficiente utilizzare il comando apache2ctl configtest.

Apache è un server modulare, questo significa che pochi moduli sono abilitati nel core del programma, è possibile però caricarli con la direttiva LoadModule, ed in particolare possono essere create direttive condizionali in base alla presenza di determinati moduli (<IfModule>)

Per verificare quali moduli sono abilitati con la versione in esecuzione è sufficiente il comando apache2 -l

Tutte le direttive che vengono associate al file di configurazione generale avranno effetto sul comportamento del server globale, è però possibile vincolare dei comportamenti solo a determinate directory, file o locazioni grazie alle voci:

• <Directory>

• <DirectoryMatch>

• <Files>

• <FilesMatch>

• <Location>

• <LocationMatch>

In più il nostro Server Web è in grado di servire più siti web in modo contemporaneo grazie all’utilizzo della direttiva <VirtualHost>, all’interno della quale si possono specificare i comportamenti particolari di ogni sito.

L’ultimo argomento riguardante il file di configurazione di apache è il file .htaccess; questo solitamente viene identificato dalla presenza in una determinata posizione del sito di un file .htaccess. La presenza di tale file permette ad apache di decentralizzare la gestione dei file di configurazione, lasciando che le direttive presenti in tale file si applichino a tutti i file e le sottodirectory della locazione corrente del file in questione.

Il file può assumere un nome diverso rispetto ad htaccess, l’importante che venga identificato dalla direttiva AccessFileName, in più esiste una seconda direttiva AllowOverride che permette all’amministratore del server web di controllare quali direttive sono lecite all’interno del file .htaccess

Hmm. I haven’t updated for four days. Feels like forever.
Normally, this would be a long post, but it’s nearly six a.m. and I’m tired so I won’t make it too long.
The MDR EX-500’s are still sounding really sweet, though I’m not enjoying them as much as I did the Skullcandy Smokin’ Buds.

Firstly, they came free because I had a Kondor voucher with my then-new phone. Secondly, I had pure unadulterated fun with those – I would blast music as loud as I wanted without a care in the world. I had great times and I had bad times, but sticking those in my ears and playing some good music always made me feel great.

I don’t get that with the Sony pair. I’m being careful not to break them or damage them. I’m worrying about how much slack there is on the wire and whether it’s in a position in which it could get damage. Sound leakage is pretty bad too, especially compared to the Skullcandy, so I have to consider the people around me.
Is this a sign that I’m growing up?

University has been a fairly hot topic over the last few days. The way it seems is that I’ll be staying in Birmingham, still living with my parents. Exactly what I didn’t want. I want to learn to be independent – to know how to survive when I know there’s nobody around. I proposed a compromise – living in student accommodation, but stay in Birmingham. That way I’m not far away but I still have the independence I want so much. My sisters both said the obvious: “It’s a complete waste of money”. I mentioned it to mum and she didn’t say much, other than one sister is moving out, she’ll get the next one married off, my brother and his family will move out and she and dad will go to another country – then I’ll get my independence and experience of living alone.
I’ll take that as a no then, shall I?

My room should start coming along soon. My sister’s new house is well under way so in a week a two, my bed will be moved into her new spare room. I’ve decided I’m not going to replace it as beds take up too much unnecessary space, and proved my point by sleeping on the floor this whole week. Dad has agreed to letting me do that. That means that all I need for my room is a wardrobe, computer desk and a soft corner.

College is still a bit of a joke, but it’s slowly getting better. I think most of my resentment towards the place is now just residue from the appalling first few weeks, which is occasionally added to by something stupid. I finished the website design and put it live onto my host. I hate it when free web hosts handicap the service by doing stuff like restricting .htaccess/.htpasswd, and only enable it for a fee. It means that I can’t provide basic password protection on the site. My old hosting account at 110mb.com is still active from when I used to use it to host my MySearchFunds/MyHPF cheat bot (an auto-searcher for a paid-to-search website). 110mb.com, at the moment, only offer 110mb worth of web space with 10gb of bandwidth. Yes, sounds logical, after all, the name is 110mb.com. But when I registered, it was 5gb of web space and 30gb of bandwidth. I logged in…I still have it Unfortunately, that is one of the sites that cripple htaccess.
I’m using Awardspace to host my assignment. Nothing special about it, but it’s really annoying that it hijacks error pages with it’s own bullshit for free users. That alone might convince me to go back to 110mb, provided that they don’t do it too. Or I could just borrow some web space from dad’s hosting account – that’s paid hosting so I get what I want.

Ayesha invited me to a birthday party of some sort. Her boyfriend is arranging it and she doesn’t know the details so she’s told me to ask him. Part of me doesn’t want to go. Every time I think of her, I think of how I feel felt about her. But she’s still a really good friend and I miss her.
I don’t know whether to go or not. Depends on whether I can even make it.

Why is it that whenever there’s a girl I might like, there’s always a caveat? I don’t know how to play for fun so I play for keeps. Playing for keeps means I have to take a bunch of things into consideration, but so far, the only girls I’ve been interested in have all had something that’s made me pull back. Some were taken, some were too far away, some were just incompatible and some were just skin deep.
It does wonders to the self-esteem when you’re nearly 18 and your greatest achievement with the opposite gender was holding hands, which took nearly two years to get to.

But it’s okay, this is just a passing phase. I’ll wake up in the morning to the sound of my niece whining and I’ll remember exactly why I’ll avoid getting married; to avoid having kids. Having kids puts me at risk of asking the question “Why should I have to take the kids to counselling? I’m not even the one who loves them.”. I am pretty heartless. She was doing my head in while I was trying to fix my brothers laptop, asking for a duck video (some sort of nursery rhyme video my brother had) and wouldn’t shut up, so I told her the duck is dead.

Speaking of my brothers laptop, he put the new 320gb hard drive in it. It’s a Dell Inspiron 9300 – quite old; the BIOS is dated 2005. Yeah, an old BIOS. Doesn’t make for good compatibility with new hard drives.
Apparently, this BIOS isn’t 48-bit LBA compatible, so it would only see 137gb of the hard drive. I managed to get it working though. Created a 100gb partition and installed XP on it. Then tweaked the registry; adding a EnableBigLba key to it. Reboot, load up Acronis Disk Director and create a new partition on the 200gb that just showed up.

Alexandra Burke’s new album, Overcome, will be out on Monday. I’ve listened to it and found a few tracks I like. Bad Boyz, which is the A-side I guess, annoys the hell out of me. The song itself is okay, but there’s a line at 0:30; I think she says “It feels my heart’s divided”, is exactly like another song. I mean completely identical in tune – just change the lyrics to match the other song and it’ll be almost an exact copy of it.
But I can’t figure out what song it is. It’s one I like, but it reminds me of bad times at school, meaning I probably deleted it when I wiped half my collection a while back. Oh, and the “Uay, uah” in the song is just a piss take. Which deaf idiot thought that was a good idea?
The other songs I like are The Silence, Dumb and Gotta Go.
Gotta Go and The Silence make me think of Ayesha. =/

Oh, I was told today that Syncrosoft’s copy protection was finally broken by AiR. It’s the copy protection used in Steinberg software like Cubase and Nuendo, and has until now, been uncrackable. I know wannabe DJ I used to be friends with at school who would have wet dreams about getting Cubase. He’s been trying to add me on facebook for a few months and I kept denying him because I still hate him for some of the stuff he said to me. I was so tempted to add him on facebook just to rub it in his nose that I can get it and he can’t.
Kudos to AiR though – epic skills there. It makes me think though, imagine if the cracking teams were on the other side, creating the copy protection software. It’d actually be pretty cool to see what sort of stuff these guys can come up with. Microsoft should hire them :p

So much for a short post.

In order to achieve the centralised (it’s not a typo, I’m an Aussie) parser outlined in the framework architecture we will need to have all relevant requests directed to index.php and block direct requests to any PHP page. For this, Apache’s mod_rewrite is a perfect tool and I will assume that you have some knowledge of regular expressions (there are great cheat sheets available for both mod_rewrite and regular expressions).

Here we will be dealing with the path of the URL (the part that tells the server what page is being requested). This is generally separated into a directory structure by forward slashes (/). The URL conventions are:

• Allowed characters are alpha (a-z), numeric (0-9), hyphen (-) and underscore (_)
• A trailing slash (/) will be treated as if the directory index has been requested
• The directory index is called main
• At least one page or directory is required
• URLs have no extension

This first rule matches for a URL with any number of directories (zero or more) as well as a specific file:

RewriteRule ^([a-z0-9_-]+)((\/[a-z0-9_-]+)*)$ index.php?page=$1$2 [NC,L,QSA]

The first set of parentheses match the mandatory page or directory. The second set is almost identical except for the fact that every remaining part will be prefixed with a slash (/). This path is then concatenated as a single string and passed to index.php for handling. Note that it is not case-sensitive (NC), it is a final match (L) and any query string is still passed (QSA).

A couple of examples:

• my-path is rewritten as index.php?page=my-path
• directory/structure/to/my-path is matched as $1 = directory while $2 = /structure/to/my-path and is rewritten as index.php?page=directory/structure/to/my-path

This second rule is almost identical to the first. The only difference is the inclusion of a trailing slash which, as described in the conventions, is a request for the directory index called main.

RewriteRule ^([a-z0-9_-]+)((\/[a-z0-9_-]+)*)\/$ index.php?page=$1$2/main [nc,L,QSA]

An example:

• directory/ is equivalent to directory/main and is rewritten as index.php?page=directory/main

I am by no means an expert in mod_rewrite nor regular expressions and I am quite confident that the efficiency of these two rules can be greatly improved. If you have any suggestions please post them as comments.

Current text version of .htaccess

Di beberapa web server (Apache paling umum),. Htaccess (hypertext akses) adalah nama standar direktori tingkat-file konfigurasi yang memungkinkan desentralisasi pengelolaan konfigurasi server web. File. Htaccess ditempatkan di dalam pohon web, dan mampu mengesampingkan subset dari server konfigurasi global; sejauh mana bagian ini didefinisikan oleh administrator server web. [1] tujuan awal. Htaccess adalah untuk memungkinkan setiap -kontrol akses direktori (misalnya memerlukan password untuk mengakses konten), maka nama itu. Saat ini. Htaccess dapat menggantikan pengaturan konfigurasi lainnya, terutama yang berkaitan dengan kontrol konten, misalnya jenis konten dan karakter set, CGI handler, dll

Pada server web Apache, maka format. Htaccess adalah sama dengan server file konfigurasi global; [2] server web lainnya (seperti Sun Java System Web Server dan Zeus Web Server) menerapkan sintaks yang sama, meskipun mereka file konfigurasi sangat berbeda. Petunjuk dalam file. Htaccess berlaku untuk direktori saat ini, dan untuk semua sub-direktori (kecuali secara eksplisit dinonaktifkan dalam konfigurasi server), tetapi karena alasan kinerja dan keamanan, tidak dapat mempengaruhi orangtua mereka direktori.

Nama file diawali dengan sebuah titik karena titik-file adalah dengan konvensi file tersembunyi di Unix-sistem operasi mirip.

Catatan penting untuk .Htaccess

Sebagai file konfigurasi,. Htaccess adalah sangat kuat. Bahkan sedikit kesalahan sintaks (seperti ruang yang hilang) dapat mengakibatkan server parah kerusakan. Jadi, adalah penting untuk membuat salinan cadangan dari segala sesuatu yang berhubungan dengan situs Anda (termasuk asli. Htaccess file) sebelum bekerja dengan Anda akses Hypertext file (s). Hal ini juga penting untuk memeriksa seluruh situs anda bersih setelah melakukan perubahan apapun untuk Anda. Htaccess file. Jika ada kesalahan atau masalah lain yang dihadapi, menggunakan backup Anda segera untuk mengembalikan fungsi asli.

Kinerja .htaccess:

. htaccess arahan menyediakan tingkat direktori konfigurasi tanpa memerlukan akses ke server utama Apache cofiguration file (httpd.conf). Namun, karena kinerja dan keamanan, file konfigurasi utama yang harus selalu digunakan untuk server arahan bila memungkinkan. Sebagai contoh, ketika server dikonfigurasi untuk memproses. Htaccess arahan, Apache harus mencari setiap direktori di dalam domain dan beban setiap dan semua. Htaccess file atas setiap dokumen permintaan. Hal ini mengakibatkan meningkatnya waktu proses halaman dan dengan demikian kinerja berkurang. Seperti memukul kinerja dapat unnoticeable untuk situs dengan lalu lintas ringan, tetapi menjadi masalah yang lebih serius untuk lebih populer website. Oleh karena itu,. Htaccess file hanya boleh digunakan ketika server utama file konfigurasi tidak dapat diakses. Lihat “Kinerja Trik” bagian dari artikel ini untuk informasi lebih lanjut.

Contoh sample.htaccess:
# enable allowoverride privileges

AllowOverride Options

# prevent viewing of a specific file

order allow,deny
deny from all

# prevent folder listing
IndexIgnore *

# prevent display of select file types
IndexIgnore *.wmv *.mp4 *.avi *.etc

# disable directory browsing
Options All -Indexes

order allow,deny
deny from all

IndexIgnore */*
AddHandler application/x-httpd-php5 .htm

sumber: (internet)