![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Except when you work for a company that considers use of includes a potential security risk. Therefore bars their use. Includes can be ASP files... What kind of "risk" does the company worry about? Thierry Mark Morse wrote: Hmm - I read those TN's and didn't see that. Is it the one I usually post? It's really old. Pre UD I think. Perhaps conventional wisdom has changed since then. Still, to this day, I see far greater numbers of sites using root rather than document relative links. |
#12
| |||
| |||
|
|
Murray, Thiery, I really don't know what the exact issue is. The company had some firm come in and audit it's IT setup. Something to do with Sarbanes Oxley compliance and the use of includes was deemed a potential security issue. That's all I know. Whether it's a red herring or not is anybody's guess. mark |
#13
| |||
| |||
|
|
My guess is that they were referring to the *file* directive, and that's what IIS6 addresses. Thierry Mark Morse wrote: Murray, Thiery, I really don't know what the exact issue is. The company had some firm come in and audit it's IT setup. Something to do with Sarbanes Oxley compliance and the use of includes was deemed a potential security issue. That's all I know. Whether it's a red herring or not is anybody's guess. mark |
#14
| |||
| |||
|
|
Thierry: So - what does the "virtual" directive do then? |
#15
| |||
| |||
|
|
With "virtual", there is no way to "map" (I'm not sure that the good english word though) the *folders/files* hierarchy because it doesn't deal with the "files system". With that directive there is only one point of entry: the root level (for the server point of view). I hope I made myself clear ![]() Thierry Murray *TMM* wrote: Thierry: So - what does the "virtual" directive do then? |
#16
| |||
| |||
|
|
Hi Murray, No, as we discussed, it concerns directories *above* the file containing the include. It's to prevent people from accessing folders above the root (they could use ../../../). That's gonna be a problem for a lot of folks when WHCs update their software... Thierry Murray *TMM* wrote: Thierry: Isn't it to directories above the root? |
#17
| |||
| |||
|
|
OK - that's what I thought. So using virtual, I could, indeed select include files that are above the containing file's location, just not outside the site's root. Right? |
#18
| |||
| |||
|
|
On Fri, 11 Jun 2004 12:26:15 -0700, "Thierry Koblentz" thierry (AT) 212Utah (DOT) invalid> wrote: And don't you just have to enable parent paths? What about accessing a database that's stored outside of the site root? My understanding was that it is far more secure to have the db NOT within the site. For example, the host I generally use has this structure for a given website on their Windows servers: /database /logs /www That's what I see when I FTP. Any Access databases would reside in /database, while all of the site files are in /www. I use DSN-less connections -- all of which MUST have ../ in the path from the site root (and multiples -- ../../ etc. -- from deeper within the site if required). Win |
#19
| |||
| |||
|
|
With virtual, you can select *any* files within the "virtual directoy". For example the virtual directive in here: www.mysite.com/dreamweaver/test/murray.shtml will let you select any files seating below this level: www.mysite.com/ It could be seating all the way up: www.mysite.com/murray.inc But it won't go any higher than that. Thierry Murray *TMM* wrote: OK - that's what I thought. So using virtual, I could, indeed select include files that are above the containing file's location, just not outside the site's root. Right? |
#20
| |||
| |||
|
|
Thierry, I assume you are referring to an IIS server. Does this hold true for any version of IIS? I thought you were supposed to use "file" instead of "virtual" for IIS servers. Do you have to use .shtml or shtm extensions for pages containing includes or is that an administrator preference? Thanks mark |
![]() |
| Thread Tools | |
| Display Modes | |
| |