Microsoft Publisher - ssl certificate

Author

ssl certificate

wolf river

2007-01-27, 10:40 pm

I have received directions on how to change the url of one of my web pages so
that it can use my web servers shared ssl certificate. I went to web page
options and manually changed the file name to one that was given to me by the
web server. I cannot get the little lock icon to show in the lower tray, and
I notice after the page load that the url has publisher's url and the url I
manually entered.

Seems that despite naming my own url publisher still has automatically named
the page too. What am I doing wrong?

DavidF

2007-01-27, 10:40 pm

Your question is unclear. If you changed the name of the page by Tools > Web
Page Options to "newname", then Publish to the Web, the Publisher will
produce an index.htm file and a index_files folder. In that folder you will
have a file called newname.htm for the page that was renamed. The URL to
that page will be http://yoursite.com/index_files/newname.htm . Give us an
example of the URL or path you are trying to achieve. How must it be
different than the way Publisher works by default?

DavidF

"wolf river" <wolfriver@discussions.microsoft.com> wrote in message
news:D2BA7BD6-F91F-4A77-AEDD-551F0C8A648E@microsoft.com...
>I have received directions on how to change the url of one of my web pages
>so
> that it can use my web servers shared ssl certificate. I went to web page
> options and manually changed the file name to one that was given to me by
> the
> web server. I cannot get the little lock icon to show in the lower tray,
> and
> I notice after the page load that the url has publisher's url and the url
> I
> manually entered.
>
> Seems that despite naming my own url publisher still has automatically
> named
> the page too. What am I doing wrong?

wolf river

2007-01-27, 10:40 pm

David, thank you for your reply. I apologize if my question was confusing. I
use ws_ftp to upload my site. In the Remote System, the index_files folder
shows the new name I entered. The problem is that the published webpage's
url contains both the url automatically generated by publisher and the
newname I asked it to use.
This is the url that I was instructed to use to access the web server's
shared ssl certificate and enterd manually using web options:
httpsssl136chihostcom~mhsaindex_filesPage519

This is the url that shows when viewing the webpage:
http://www.friendsofmhsa.com/index_...lesPage519.htm.
The webpage loads properly but does not have the little lock icon in the
lower tray.

Using Tools, then, Web Page Options, to name the url seems self-explanitory
and I felt confident that I had executed the request correctly. But, perhaps
I am not using that tool correctly?

"DavidF" wrote:

> Your question is unclear. If you changed the name of the page by Tools > Web
> Page Options to "newname", then Publish to the Web, the Publisher will
> produce an index.htm file and a index_files folder. In that folder you will
> have a file called newname.htm for the page that was renamed. The URL to
> that page will be http://yoursite.com/index_files/newname.htm . Give us an
> example of the URL or path you are trying to achieve. How must it be
> different than the way Publisher works by default?
>
> DavidF
>
> "wolf river" <wolfriver@discussions.microsoft.com> wrote in message
> news:D2BA7BD6-F91F-4A77-AEDD-551F0C8A648E@microsoft.com...
>
>
>

Mike Koewler

2007-01-27, 10:40 pm

wolf,

I haven't done any SSL pages but don't you have to upload them to the
https (note the s) folder?

Mike

wolf river wrote:
[color=darkred]
> David, thank you for your reply. I apologize if my question was confusing. I
> use ws_ftp to upload my site. In the Remote System, the index_files folder
> shows the new name I entered. The problem is that the published webpage's
> url contains both the url automatically generated by publisher and the
> newname I asked it to use.
> This is the url that I was instructed to use to access the web server's
> shared ssl certificate and enterd manually using web options:
> httpsssl136chihostcom~mhsaindex_filesPage519
>
> This is the url that shows when viewing the webpage:
> http://www.friendsofmhsa.com/index_...lesPage519.htm.
> The webpage loads properly but does not have the little lock icon in the
> lower tray.
>
> Using Tools, then, Web Page Options, to name the url seems self-explanitory
> and I felt confident that I had executed the request correctly. But, perhaps
> I am not using that tool correctly?
>
>
>
> "DavidF" wrote:
>
>

wolf river

2007-01-27, 10:40 pm

"Uploading files to the https folder": Isn't that what a person is asking
Publisher to do when you rename the file in web options? https is part of the
new name. The renamed url is written exactly as it was given to me by my
webserver. What am I missing?

"Mike Koewler" wrote:

> wolf,
>
> I haven't done any SSL pages but don't you have to upload them to the
> https (note the s) folder?
>
> Mike
>
> wolf river wrote:
>
>

Mike Koewler

2007-01-27, 10:40 pm

wolf,

No. Renaming the file, uh, renames the file. You need to upload it -
whatever the name, to the https folder, then put a link to that file
(https://www.yourdomain.com/pagename.htm). IOW, upload your files not to
public_html but to httpsdocs (or whatever your secure area is called).

Mike

wolf river wrote:
[color=darkred]
> "Uploading files to the https folder": Isn't that what a person is asking
> Publisher to do when you rename the file in web options? https is part of the
> new name. The renamed url is written exactly as it was given to me by my
> webserver. What am I missing?
>
> "Mike Koewler" wrote:
>
>

wolf river

2007-01-27, 10:40 pm

Thanks Mike. I understand what you are saying. The last time I contacted the
webserver tech support they did not mention uploading the page to a
particular https folder instead of public_html. I will re-contact them.

"Mike Koewler" wrote:

> wolf,
>
> No. Renaming the file, uh, renames the file. You need to upload it -
> whatever the name, to the https folder, then put a link to that file
> (https://www.yourdomain.com/pagename.htm). IOW, upload your files not to
> public_html but to httpsdocs (or whatever your secure area is called).
>
> Mike
>
> wolf river wrote:
>
>