Re: gettin parameters from url, architecture question

they are dynamic. Would it make sence to put all requests to an error document? Is this not a huge load for the server? Lets say I redirect all 401 errors to one php page where I parse the url and find the right file to redirect. This would be possible, but I fear that it would slow down the server. What do you think? Maybe there is another possiblitiy=? Merlin -- &lt;IFRAME SRC="http://saratoga.globosapiens/associates/report_member.php?u=3&color=EEE EEE" scrolling=no frameborder=0 TITLE="My travel articles" width="330" height="155" ALLOWTRANSPARENCY="true"><a href="http://www.globosapiens.net" title="Worldwide Travel Community"a>Travel Community<a/> </IFRAME> "Curt Zirzow" <curt@zirzow.dyndns.org> schrieb im Newsbeitrag news:20030805140427.GZ21938@bagend.shire... > * Thus wrote Merlin (news.groups@web.de): > > Hi there, > > > > I recently dumped into a site which was kind of search engine optimized. > > They had urls like this: > > > > server.com/country_province_city_222.html > > > > where country would be a php file, but how are those guys picking the right > > file? Where is the php file stored and how does the server know which file > > to call?? > > > > Can anybody shed a bit of lite on that? ;-) > > It almost looks to me that those are static pages. but if they > aren't a simple way to handle that would be to set your > ErrorDocument in the webserver. > > > Curt > -- > "I used to think I was indecisive, but now I'm not so sure." >