- From: Vishal Wani <vishal@nectech.com>
- Date: Fri, 29 Oct 1999 09:40:17 -0400
- To: "Michele Lee" <mclee@oblix.com>, <www-talk@w3.org>
What web server do you have ? if it's IIS then you can go to IIS administration and under directory security option for your default / any website.....you will see basically three ways you could give access to web server. 1. Anonymus access 2. Basic Authentication 3. Digest Access Authentication.(on Windows NT - windows NT Challange/Response mechanism) In basic uthentication user is asked the Login and password but this information is not encrypted....whereas with DAA(windows NT Challange/Response mechanism) the password and Login information is encrypted and sent. In both these methods access is restricted using NTFS access control list (on NT machine...I do not now how it works on other systems...but should be same as this is not really specific to NT but rather it's HTTP) This actually is HTTP property itself and not any web-server specific...so you could find a way to turn it on in any web-server. It's very easy to implement any of these. For more info you can search on W3C site for Basic and DAA under HTTP Protocol - security issues... I hope that helps. Vishal ----- Original Message ----- From: Michele Lee <mclee@oblix.com> To: <www-talk@w3.org> Sent: Thursday, October 28, 1999 5:38 PM Subject: HTTP authentication software > Hi, > > Are there any software that performs HTTP authentication? In particular, I > have an server application that resides on a web server, and I want to write a > non-browser client application that can talk to the server app. I'm concerned > about how my client app can authenticate with the web server. If there are > existing software that I can use, that would be great. Otherwise, is it > difficult to write my own? > > thanks, > > --Michele > >
Received on Friday, 29 October 1999 09:31:24 UTC