Tom: I have used the _private folders for all my include pages beginning
with the 98 extensions and now the 2000 extensions and have no problems
whatsoever.
Of course, linking to pages within the _private folders gives a forbidden
access.
--
===
Tom [Pepper] Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/
===
|I see!
|
| I haven't tested this over the years, because back with the FP98
extensions and maybe with the first
| version of the FP2000 extensions, as long as you have the URL to a file in
the _private folder you
| could still access the file, the permissions at the time were set to allow
forms and the hit counter
| to be able to write to files in the _private folder but did not stop them
from being viewed.
|
| But now that the _private folder is protected that means you can't have
links to any pages or
| include page within it, since a site visitor would be prompted for a
login, correct?
|
| --
| ==============================================
| Thomas A. Rowe (Microsoft MVP - FrontPage)
| ==============================================
| If you feel your current issue is a results of installing
| a Service Pack or security update, please contact
| Microsoft Product Support Services:
|
http://support.microsoft.com
| If the problem can be shown to have been caused by a
| security update, then there is usually no charge for the call.
| ==============================================
|
| | > Guess permissions are not set properly. Mine give forbidden access 403.
| > --
| > Tom [Pepper] Willett
| > Microsoft MVP - FrontPage
| > FrontPage Support:
http://www.frontpagemvps.com/
| > ----------
| >> Example:
| >>
http://www.ecom-data.com/_private/test.htm
| >>
| >> --
| >> ==============================================
| >> Thomas A. Rowe (Microsoft MVP - FrontPage)
| >> ==============================================
| >> If you feel your current issue is a results of installing
| >> a Service Pack or security update, please contact
| >> Microsoft Product Support Services:
| >>
http://support.microsoft.com
| >> If the problem can be shown to have been caused by a
| >> security update, then there is usually no charge for the call.
| >> ==============================================
| >>
| >> | >>> Since the FP _private folder is permissions protected, and cannot be
entered via a browser, how
| >>> can the search engines get to the material?
| >>> --
| >>> Tom [Pepper] Willett
| >>> Microsoft MVP - FrontPage
| >>> FrontPage Support:
http://www.frontpagemvps.com/
| >>> ----------
| >>> | >>>> First, moving the files to the FP _private folder will not protect
them from search engines,
| >>>> such as Google, MSN, Yahoo, etc. only from the FP search component.
| >>>>
| >>>> You have to answer YES.
| >>>>
| >>>> If you don't need the file in your site, then you should delete them
from the site. Export them
| >>>> to a folder on your HD.
| >>>>
| >>>> --
| >>>> ==============================================
| >>>> Thomas A. Rowe (Microsoft MVP - FrontPage)
| >>>> ==============================================
| >>>> If you feel your current issue is a results of installing
| >>>> a Service Pack or security update, please contact
| >>>> Microsoft Product Support Services:
| >>>>
http://support.microsoft.com
| >>>> If the problem can be shown to have been caused by a
| >>>> security update, then there is usually no charge for the call.
| >>>> ==============================================
| >>>>
| >>>> | >>>>> I'm moving some old files into my _private folder (for the first
time) so
| >>>>> their not picked up by search engines. After I've moved the files
into the
| >>>>> _private folder and try to publish, I get the message that says: "Do
you want
| >>>>> to remove this file? The file exists on the destination server but
does not
| >>>>> exist on the current web site. Do you want FP to remove it from
| >>>>>
www.mysite.com?" Should I say yes or no? I don't want to permanently
delete
| >>>>> anything and I don't quite know what it's asking.
| >>>>
| >>>>
| >>>
| >>>
| >>
| >>
| >
| >
|
|