Wildpath implementation

Comments:

Author Thread:

j.merrill

Wildpath implementation
Posted: Saturday, May 08, 2004 3:18 PM (EST)

I don't "know" but I'm of the strong impression that the ONLY paths are virtual. That is, there's no way to get to the contents of any directory that isn't defined via a virtual path (or presented as if it were part of a VP using the wildcard mechanism). Think about it -- you do not want callers to be able to get at any files on your disk, unless you have specifically set things up to allow that. Right?


fred.waid

Wildpath implementation
Posted: Saturday, May 08, 2004 5:22 PM (EST)

J is just about right. The only files that the server will return itself are those located in the folder you choose as your public folder and it's subfolders. This is done on the "home directory" tab, .

The order of checking for paths are:

Virtual Path (exact match)

Wild Path (root match)

Real Path

While we are on the path issue, don't forget we have the scripts filters, which is used to filter a path before the path is processed.   For instance if we had paths of the format:

http://www.yourserver.com/test/what/isapi.dll?/images/picture.gif

you could enter /test/what/isapi.dll? as your filter and then the path after filtering would be:

/images/picture.gif

This is particuarly useful when you have a site which needs to be both accessed directly and also from a an IIS server (or servers) using an isapi forwarder, asp forwarder, or java forwarder. This means that you could have a customer running IIS or APACHE and returning pages from your server. The customer could manage security, logins, etc, all based on their domain, and return your pages. With these types of forwarders the client only sees the original domain, with IIS or APACHE actually returning the page you create.



davin.church

Wildpath implementation
Posted: Saturday, May 08, 2004 8:38 PM (EST)

Oh, good! That's what I was asking -- it will check for virtual/wild paths before real ones.

Thanks