That's what I do, and it's really swift of doing, even though you
never saw an htaccess file.
I use it, there are some disadvantages on server load but in my
projects, I don't care. Well, it works as expected.
Best regards,
Eugenio Costa.
On 3/1/07, Adrian Lynch [EMAIL PROTECTED] wrote:
Or
The webmaster I'm talking to is responsible for URLs that end like this
*.cfm?doc_id=n ... and thinks it's perfectly acceptable
In that case, the webmaster is making dynamically generated pages.
URLs that end like that are necessary, because they're used to pass
variables to the page. The
On 01/03/2007, at 11:36 AM, Kenny Graham wrote:
The webmaster I'm talking to is responsible for URLs that end like
this
*.cfm?doc_id=n ... and thinks it's perfectly acceptable
. Beyond that, any way to get rid of the ?doc_id=n and
such at the ends of the URLs would require an
Hi folks,
I followed a recent thread here on how people manage their links, and I made
a request to our organisation's webmaster to allow MultiViews for my
department's website (which I manage, and which is part of a large public
organisation). I have a penchant for short, usable URLs that don't
On 01/03/2007, at 9:31 AM, libwebdev wrote:
Hi folks,
I followed a recent thread here on how people manage their links,
and I made a request to our organisation's webmaster to allow
MultiViews for my department's website (which I manage, and which
is part of a large public
I appreciate your comments, Breton, thank you.
At 11:19 AM 1/03/2007 +1100, Breton Slivka wrote:
Given the structure of the department site, I am not sure that
there is any great advantage to be gained.'
what special qualities of the site's structure is he talking about here?
No special
organisation). I have a penchant for short, usable URLs that don't show file
names, and would like to link to /mydept/training/ rather than
/mydept/training.htm.
Sounds a lot like you'll get resistance, although I agree that not
showing extensions has some benefits.
I'd shoot for a middle of
