|
|
You're in the
iis security
group:SSL entire web site
iis security:
We will be launching a new WWW site in the next few weeks, and for internal
reasons (reasons I can't go into here), the new web site will need to be entirely https. I'm trying to determine what issues, if any, there will be when doing this. The new site is entirely different, so we expect issues anyway with people finding things via search engines. Of course, bookmarks would have been an issue anyway since the site is entirely different. I can see one issue is that if someone types in http://www..., but we can redirect them to the https site. So what issues can I expect if our entire site is https? Thanks! Doug
issue? not much....
things to consider is this will increase resouse usage for cpu/ram/etc as know iis needs to https first also if you have non https url? you might get prompt saying 'the page content secure / nonsecure url' etc warning. -- Regards, Bernard Cheah http://www.iis.net/ http://www.iis-resources.com/ http://msmvps.com/blogs/bernard/ [quoted text, click to view] "Doug" <dgeiste@REMOVEsnet.net> wrote in message news:EPzSg.9171$6S3.332@newssvr25.news.prodigy.net... > We will be launching a new WWW site in the next few weeks, and for > internal reasons (reasons I can't go into here), the new web site will > need to be entirely https. I'm trying to determine what issues, if any, > there will be when doing this. > > The new site is entirely different, so we expect issues anyway with people > finding things via search engines. Of course, bookmarks would have been an > issue anyway since the site is entirely different. > > I can see one issue is that if someone types in http://www..., but we can > redirect them to the https site. > > So what issues can I expect if our entire site is https? > > Thanks! > Doug > > >
Thanks Bernard. I didn't think abut the RAM/CPU usage.
The issue of getting the https error message is problem. If the end user types in www.domainname.com/somepage.html, they'll get the https error. Because we also do radio ads to content on our site, it would also mean the that the annoucer would have to say, "https://...", which no one will get because they're not used to typing, having to type it in,... or hearing https. So based on this, I've convinced those that securing individual pages makes a lot more sense than the entire site. Thanks for the response. Much appreciated! Doug [quoted text, click to view] "Bernard Cheah [MVP]" <qbernard@hotmail.com.discuss> wrote in message news:uEPCys34GHA.2144@TK2MSFTNGP04.phx.gbl... > issue? not much.... > things to consider is this will increase resouse usage for cpu/ram/etc as > know iis needs to https first > also if you have non https url? you might get prompt saying 'the page > content secure / nonsecure url' etc warning. > > > -- > Regards, > Bernard Cheah > http://www.iis.net/ > http://www.iis-resources.com/ > http://msmvps.com/blogs/bernard/ > > > "Doug" <dgeiste@REMOVEsnet.net> wrote in message > news:EPzSg.9171$6S3.332@newssvr25.news.prodigy.net... >> We will be launching a new WWW site in the next few weeks, and for >> internal reasons (reasons I can't go into here), the new web site will >> need to be entirely https. I'm trying to determine what issues, if any, >> there will be when doing this. >> >> The new site is entirely different, so we expect issues anyway with >> people finding things via search engines. Of course, bookmarks would have >> been an issue anyway since the site is entirely different. >> >> I can see one issue is that if someone types in http://www..., but we can >> redirect them to the https site. >> >> So what issues can I expect if our entire site is https? >> >> Thanks! >> Doug >> >> >> > >
You can always force user and redirect to https pages...
for example. HOW TO: Use ASP to Force SSL for Specific Pages http://support.microsoft.com/?id=239875 -- Regards, Bernard Cheah http://www.iis.net/ http://www.iis-resources.com/ http://msmvps.com/blogs/bernard/ [quoted text, click to view] "Doug" <dgeiste@REMOVEsnet.net> wrote in message news:fJaTg.5879$TV3.5644@newssvr21.news.prodigy.com... > Thanks Bernard. I didn't think abut the RAM/CPU usage. > > The issue of getting the https error message is problem. If the end user > types in www.domainname.com/somepage.html, they'll get the https error. > Because we also do radio ads to content on our site, it would also mean > the that the annoucer would have to say, "https://...", which no one will > get because they're not used to typing, having to type it in,... or > hearing https. > > So based on this, I've convinced those that securing individual pages > makes a lot more sense than the entire site. > > Thanks for the response. Much appreciated! > > Doug > > > "Bernard Cheah [MVP]" <qbernard@hotmail.com.discuss> wrote in message > news:uEPCys34GHA.2144@TK2MSFTNGP04.phx.gbl... >> issue? not much.... >> things to consider is this will increase resouse usage for cpu/ram/etc as >> know iis needs to https first >> also if you have non https url? you might get prompt saying 'the page >> content secure / nonsecure url' etc warning. >> >> >> -- >> Regards, >> Bernard Cheah >> http://www.iis.net/ >> http://www.iis-resources.com/ >> http://msmvps.com/blogs/bernard/ >> >> >> "Doug" <dgeiste@REMOVEsnet.net> wrote in message >> news:EPzSg.9171$6S3.332@newssvr25.news.prodigy.net... >>> We will be launching a new WWW site in the next few weeks, and for >>> internal reasons (reasons I can't go into here), the new web site will >>> need to be entirely https. I'm trying to determine what issues, if any, >>> there will be when doing this. >>> >>> The new site is entirely different, so we expect issues anyway with >>> people finding things via search engines. Of course, bookmarks would >>> have been an issue anyway since the site is entirely different. >>> >>> I can see one issue is that if someone types in http://www..., but we >>> can redirect them to the https site. >>> >>> So what issues can I expect if our entire site is https? >>> >>> Thanks! >>> Doug >>> >>> >>> >> >> > >
Thanks. This could work.
[quoted text, click to view] "Bernard Cheah [MVP]" <qbernard@hotmail.com.discuss> wrote in message news:%23aWJyfT5GHA.4644@TK2MSFTNGP04.phx.gbl... > You can always force user and redirect to https pages... > for example. > HOW TO: Use ASP to Force SSL for Specific Pages > http://support.microsoft.com/?id=239875 > > -- > Regards, > Bernard Cheah > http://www.iis.net/ > http://www.iis-resources.com/ > http://msmvps.com/blogs/bernard/ > > > "Doug" <dgeiste@REMOVEsnet.net> wrote in message > news:fJaTg.5879$TV3.5644@newssvr21.news.prodigy.com... >> Thanks Bernard. I didn't think abut the RAM/CPU usage. >> >> The issue of getting the https error message is problem. If the end user >> types in www.domainname.com/somepage.html, they'll get the https error. >> Because we also do radio ads to content on our site, it would also mean >> the that the annoucer would have to say, "https://...", which no one will >> get because they're not used to typing, having to type it in,... or >> hearing https. >> >> So based on this, I've convinced those that securing individual pages >> makes a lot more sense than the entire site. >> >> Thanks for the response. Much appreciated! >> >> Doug >> >> >> "Bernard Cheah [MVP]" <qbernard@hotmail.com.discuss> wrote in message >> news:uEPCys34GHA.2144@TK2MSFTNGP04.phx.gbl... >>> issue? not much.... >>> things to consider is this will increase resouse usage for cpu/ram/etc >>> as know iis needs to https first >>> also if you have non https url? you might get prompt saying 'the page >>> content secure / nonsecure url' etc warning. >>> >>> >>> -- >>> Regards, >>> Bernard Cheah >>> http://www.iis.net/ >>> http://www.iis-resources.com/ >>> http://msmvps.com/blogs/bernard/ >>> >>> >>> "Doug" <dgeiste@REMOVEsnet.net> wrote in message >>> news:EPzSg.9171$6S3.332@newssvr25.news.prodigy.net... >>>> We will be launching a new WWW site in the next few weeks, and for >>>> internal reasons (reasons I can't go into here), the new web site will >>>> need to be entirely https. I'm trying to determine what issues, if any, >>>> there will be when doing this. >>>> >>>> The new site is entirely different, so we expect issues anyway with >>>> people finding things via search engines. Of course, bookmarks would >>>> have been an issue anyway since the site is entirely different. >>>> >>>> I can see one issue is that if someone types in http://www..., but we >>>> can redirect them to the https site. >>>> >>>> So what issues can I expect if our entire site is https? >>>> >>>> Thanks! >>>> Doug >>>> >>>> >>>> >>> >>> >> >> > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |