|
Posted by David Wang [Msft] on October 4, 2005, 3:42 am
If you were Registered and logged in, you could reply and use other advanced thread options
Only you can assess the risk since it completely depends on the
individual/organization.
My instinct is to stick with https:// only because you certainly cannot be
less secure (i.e. if you cannot correctly assess risk, then choose the less
risky/more secure choice).
Otherwise, it sounds like you set up the application (either explicitly or
involuntarily) to require HTTPS (it is not default configuration in IIS, so
either you or the custom application did this). In IIS, this is configured
by going to the property page of the application/website (Right click
properties in the IIS Manager UI), selecting the "Directory Security" tab,
clicking the "Edit" button in the "Secure communications" area, and
unchecking the "Require secure channel (SSL)" checkbox.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
It's a CRM application and yes, it's installed into IIS V6.0. We have only
one server, the Win2K3 server.
Thanks for your response!!
"IWSEC" wrote:
> Hi,
> What application is it and is it installed into IIS on your W2K3 server
or
> elsewhere?
>
> Cheers
> IWSEC
> www.iwsec.co.uk
>
> "Tom" wrote:
>
> > Win2K3 SP1
> > IE 6.0 SP1
> > I have an application that allows http:// but I can only invoke it
locally
> > or remotely via https://. What do I need to change to allow the
standard
> > http:// rather than https://? I can access the Internet normally but I
can't
> > use THIS specific application. The application technical support group
> > states that I need to setup http:// rather than https://. Since I
didn't
> > initial 'setup' anything unique, where do I go/look to make the changes?
> > What risk factors do I have here either externally or internally? We
are a
> > small office of <25 users.
> > TIA,
| 
XML site map