Of ./name.html and /name.html

Do they read from the file calling them?

[4thePegeh]

Hi

Moving

this code:

<!--#if expr="(${inclprefix} != /^$/ && ${inclprefix} != /^\(none\)$/)" -->

<!--#include virtual="${inclprefix}2.txt" -->

<!--#endif --> (kindly suggested by Mr. Morgan a year ago - and working flawlessly ever since)

from the public directory ( http://www.domain.com/file.html ) to "directory a" inside the public directory ( http://www.domain.com/a/file.html ), stopped it from working.

Reading this http://www.webmasterworld.com/forum92/4498.htm I took a chance and tested replacing ${inclprefix} with each of these:

/${inclprefix}

../${inclprefix}

/a/${inclprefix}

The first two work and the third does not.

Is it because they are interpreting the instructions from the perspective of the file that calls them?

So, /a/name.html is actually looking for http://www.domain.com/a/a/name.html?

Do either of /${inclprefix} and ../${inclprefix} raise security issues?

[g1smd]

I think the filenames are relative or absolute within the filesystem folder structure. They are NOT seen as URLs from the outside, but instead as internal folders within the server. It's only a URL when your browser requests it. This is an internal process within the server, therefore it isn't a URL as such.