ahh, I'm on a shared hosting server as of now. My website is small and only has about 50 members. When I'm able to make some more revenue, I will move to a dedicated and perhaps be able to configure it.
Sorry that I didn't mention this before. | [reply] |
If you're on apache, you can add the following to the top-level .htaccess file:
ErrorDocument 404 /404.cgi
That will internally redirect any non-found requests to /404.cgi. 404.cgi can then figure out what the original request was by examining $ENV{REQUEST_URI} and show the appropriate information (i.e a valid user page, or a 404 not found page)
In my experience, this works on lots of shared hosting solutions even if mod_rewrite isn't available.
| [reply]
[d/l] |
Clever - me like.
map{$a=1-$_/10;map{$d=$a;$e=$b=$_/20-2;map{($d,$e)=(2*$d*$e+$a,$e**2
-$d**2+$b);$c=$d**2+$e**2>4?$d=8:_}1..50;print$c}0..59;print$/}0..20
Tom Melly, pm@tomandlu.co.uk
| [reply]
[d/l] |
if you're on a shared hosting , then you probably have apache with mod_rewrite installed
and you dont have to configure anything yourself
you could you use mod_rewrite with .htaccess files
take a look at the URL i gave to you earlier
| [reply] |
Would cookies be a solution? Does path_info help?
Gotta run, but just ask if you want clarification on either of these.
map{$a=1-$_/10;map{$d=$a;$e=$b=$_/20-2;map{($d,$e)=(2*$d*$e+$a,$e**2
-$d**2+$b);$c=$d**2+$e**2>4?$d=8:_}1..50;print$c}0..59;print$/}0..20
Tom Melly, pm@tomandlu.co.uk
| [reply]
[d/l] |