I'm not going to repeat what others have said on this thread, but in the event you want to explore other ways of writing your URL's, consider using the PATH_INFO variable. This would let you construct traditional-looking URL's that are really comprised of script arguments:

http://www.example.com/one/two/three/four.html
[download]

You could create a script called 'one' in the web server's docroot, and your script would receive the following in its $ENV{PATH_INFO}:

/two/three/four.html
[download]

You could even go a step further and use this in conjunction with typical CGI arguments:

http://www.example.com/one/two.html?arg1=one&arg2=two

$ENV{PATH_INFO}    is "/one/two.html"
$ENV{QUERY_STRING} is "arg1=one&arg2=two"
[download]

CGI.pm will do all of this for you in a friendly fashion.