1) Yes of can only you can only use ASP code in a .asp page
(you only need to change the https pages, but is it always best practice
to change all pages to .asp so you don't keep popping in
and out of sessions - from .htm to .asp & reverse)
2) The FP Nav bars / bots (from Nav View) only use relative addresses
- so you can not use them to link to SSL pages
- just add normal html links after your nav bar (htm non-SSL) links
--
_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________
|I appreciate your reply Stefan, this suggestion is a short, practical
| solution - I like it.
|
| Now I have two follow-up questions
|
| a) To implement this, I'm going to have to change .htm to .asp for the
page
| suffix on all of the pages?
|
| b) Using FrontPage's navigation, once I get to the SSL part of the site,
all
| of the links back to the "non-secure" portion show up with https. I've
read
|
http://support.microsoft.com/default.aspx?scid=kb;en-us;825493, which
| states: "To link from the SSL port to the default port, use a fully
| qualified URL with the unencrypted protocol." How do I go about making
| >that< change using the FP navigation bots?
|
| Thanks again!
|
| Larry
|
|
|
| | > Common problem (even w/o the ssl)
| > - Using a local development path vs. an online server based path
| >
| > Depends on your OS and if you can use server side scripting
| >
| > If running under localhost (development path) and a Windows server
(online
| > path) that supports ASP
| > - you could create a server side include w/ the below code for all
page
| > (or just enter it in the top of affected pages)
| >
| > <%
| > Dim Location, Site
| > Location = Request.ServerVariables("SERVER_NAME")
| > If Location = "
www.website.com" Then
| > Site = "
https://www.website.com/"
| > Else
| > Site = "
http://localhost/"
| > End If
| > %>
| >
| > And for your links in any pages using the above you would enter
| > href="<%=Site%>ssl/page.htm"
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| >
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
| > _____________________________________________
| >
| >
| > | > | I've developed a web site with FrontPage and the client wanted part
of
| > the
| > | site protected with an SSL certificate. So, I created an "ssl"
folder
| > in
| > | the web to handle all of those pages, forms, and images.
| > |
| > | In my development version, I have used an anchor tag with an
| > | href="ssl/page.htm" link to get to the ssl pages. However, the
| > production
| > | version has to have the explicit anchor tag
| > | href="
https://www.website.com/ssl/page.htm" format.
| > |
| > | When I test locally, I certainly don't want to point to or go to the
| > | production web site. Does anyone have any recommendations on how I
can
| > | negotiate future changes to the pages that have links with these two
| > | different constructs?
| > |
| > | Thanks!
| > |
| > | Larry
| > |
| > |
| >
| >
|
|
