Password Protect a webpage

[Don Schmidt]

We have a Publisher 2000 created six page website www.vanusa.org

Presently we have a link on the site to a password protected folder.

Is there a way to password protect one of the pagen.html pages?

If so, how?

The method used to protect the folder is with a htaccess and a htpasswd
files.

 

[DavidF]

Hi Don,

Have you considered using a second Publisher document to create the page
that you want to protect, and then linking to it, and posting it in another
password protected folder?

DavidF

 

[Don Schmidt]

David,

My ISP offers domains with 1000 MB of server space and 5000 email addresses.
Each email address can have its own personal web page with 10 MB of server
space (not using any of the 1000 MB assigned to the domain). I thought of
creating "personal" webpage with one of the email addresses BUT, I presently
have 21 MB of files for download.

I asked the same question (password protect a webpage) to my ISP. They
provided me with a "give this a try" solution. Instead of having the
password protect a folder, try using the file name, i.e., page5.html. I
haven't tried it yet but plan to do some experimenting in a day or two.

The secret stuff adds some fun to website building.

P.S. The files we want to safeguard are Member Directory updates, Lodge
Budgets, Forms, Lodge history, backup files listing passwords, email
passwords etc.
No atomic secrets. <G>

--
Don
Vancouver, USA

Hi Don,

Have you considered using a second Publisher document to create the page
that you want to protect, and then linking to it, and posting it in
another password protected folder?

DavidF

 

[DavidF]

Don,

I suspect that what you are describing with getting 10 MB of server space
with each email address is the allocated space...the mailbox for the
messages with that email address, not a website.

I don't understand the logic behind the use of the "page5.html", but hey...I
don't follow a lot of logic.

I still would think that your host like most would offer more than one
password protected subfolder on your main site, and given that you have more
than just a page to protect, I still think producing a new web page/site
with Publisher and uploading it and the files you want to protect, to that
protected subfolder is the most "logical" solution to me...but then we have
already talked about my logic. I am fairly sure you understand what I am
proposing, but in case you don't then read David Bartosik's article about
"Building a web site with multiple Publisher web publication files":
http://msmvps.com/blogs/dbartosik/archive/2006/01/16/81264.aspx

I also seem to remember someone suggesting that there are javascript
snippets that can password protect pages, but it seems they also said they
are easily worked around....you might google that subject.

So, sorry, but my best suggestion is to create the protected subfolder, and
produce a second Publisher site and link to it...good luck, and let us know
the solution you come up with.

DavidF

David,

My ISP offers domains with 1000 MB of server space and 5000 email
addresses. Each email address can have its own personal web page with 10
MB of server space (not using any of the 1000 MB assigned to the domain).
I thought of creating "personal" webpage with one of the email addresses
BUT, I presently have 21 MB of files for download.

I asked the same question (password protect a webpage) to my ISP. They
provided me with a "give this a try" solution. Instead of having the
password protect a folder, try using the file name, i.e., page5.html. I
haven't tried it yet but plan to do some experimenting in a day or two.

The secret stuff adds some fun to website building.

P.S. The files we want to safeguard are Member Directory updates, Lodge
Budgets, Forms, Lodge history, backup files listing passwords, email
passwords etc.
No atomic secrets. <G>

 

[Don Schmidt]

Sorry I've been unclear; we presently have a subfolder protected but the
files listed look like a DOS listing. I was looking for a way to list the
files with a description, sort of what could be done using a hyperlink.

Me thinks looking for a way to password a webpage should go to the "back
burner" and get on with other chores.

Thanks for sharing thoughts.

Take care,

Don

 

[DavidF]

You can do this without creating a new protected folder. Right now your
files look like a DOS listing, as you put it because there is no index.html
file in that folder. If the browser had found an index.html file in that
folder it would have loaded it. I think there are several fairly simple way
to accomplish your goals, but it might require redoing a few links, and
doing some reorganization perhaps.

First create a new single Publisher web page that lists and describes the
files that you want to make available to download, that currently reside in
the protected folder. Looking at your home page and the link to the members
only folder, which I presume is the protected folder, that link is:
http://www.osiaglnw.org/nwin/current.pdf which tells me the protected
folder is called "nwin". This means that you will write the links on your
new one page site to that folder, and the file that you want to download and
when clicked the member will have to log in before they can download the
file. Now, I know you like relative links, and you are welcome to change
these suggestions, but I most often use absolute links, so I don't get
confused. So, after writing the descriptions to the different files that are
available to download, if you want use the "click here" approach, then
insert your hyperlinks to the different files:
http://www.osiaglnw.org/nwin/current.pdf
http://www.osiaglnw.org/nwin/adifferent.pdf
http://www.osiaglnw.org/nwin/athirdfile.pdf
etc.

Then after you have the page ready to upload, create a new subfolder on your
main site, and perhaps call it "members", and upload your new one page
Publisher website to that folder. Then from your main site somewhere, write
a link to that page:
http://www.vanusa.org/members/index.html
Then after that page loads, the member can click on any of the links and
they will require a log in just like
http://www.osiaglnw.org/nwin/current.pdf does.

Its all clear as mud now right? ;-)

DavidF

 

[Don Schmidt]

David,

You've got the wrong website. The site I'm trying to provide a protected
webpage is www.vanusa.org. It has six pages and under study is creating a
7th page listing and describing some proprietary files protected by a
password. The problems seem a bit more than worthwhile for it looks like
page 7 would have to reside in a protected folder which means the links to
page 7 on pages 1 through 6 would require altering. Also, when uploading
edited site pages it would require special handling of page 7; pages 1
through 6 would go into the public_html folder on the server and page 7
would need to go into the protected folder located inside the public_html
folder. Then there's the problem of the image files; which ones would need
to also go into the protected folder. This seems like a many martini task
which may impede efficiency. <G>

DOS listing isn't so bad after all. <G>

AND maybe a disaster if page 7 didn't get uploaded into the protected folder
but got in the same location as pages 1 through 6!

But thanks for the help.

BTW, the www.osiaglnw.org site which is in my list of chores is a "Cold
Fusion" site and I'm working with a Publisher 2000 site.

Take care,

Don
Vancouver, USA

 

[DavidF]

Ok, wrong website, and perhaps wrong structure, but the concept should work.

Right now your are creating a 6 page site and uploading it to your
public_html folder. That means that you are uploading the index.html file,
plus page2.html, page3.html, page4.html, page5.html, page6html and all the
supporting images to the public_html folder. The new Page 7 which describes
and lists the files available for download can also reside in the
public_html folder, or in the protected folder...just depends on how you
want to structure your site and where you put your protected folder.

You could just add a seventh page to your current public site, including a
navbar link, and call it Member Section or something like that. The public
could click on that link and they would be able to see the page listing the
files available to members and their description. However, when anyone
clicks on one of the file links, they are required to log in before they
will be able to download the file.

However it sounds like you want the 7th page, the page that describes and
lists the files available for downloading to also reside in the protected
folder...no problem. Once again the main question is where you put the
protected folder. If it is a subfolder of your public_html folder then I
would create another subfolder in that protected folder to contain the files
you want to make available to download to keep things organized . So,
assuming that your protected folder does reside inside your public_html
folder, and is called "members", then within that folder you would create a
subfolder called "downloads" which would contain all the files that you want
to make available to the members.

Then you would create a single page website with Publisher...the description
page for all the files available to be downloaded by the members. When you
publish that page, you will upload the index.htm file and the supporting
images to the "members" folder. The link to this members description page
from your main site would be: http://www.vanusa.org/members/index.html and
would require a log in. Then the links on the members description page to
the files available for download would be:
http://www.vanusa.org/members/downloads/filename1.pdf or perhaps
http://www.vanusa.org/members/downloads/anotherfilename.doc
etc.... When the member clicks on those links they can download the files.

Like I said, it all depends on where you place the protected folder and how
you want to structure your site. If you put the protected folder somewhere
else on your host server, then write the links accordingly. If you are
having trouble understanding how to write the links or how to structure your
site, then once again I suggest that you read David's article about building
a website with multiple Publisher files.
http://msmvps.com/blogs/dbartosik/archive/2006/01/16/81264.aspx

I hope I was a bit more clear this time...

DavidF

 

[Don Schmidt]

Thanks David. Your explanation is very clear and this ol soul is able to
understand it. I'll give it a go.

Don