J
Joe H
I have a web service that is set to use Basic Authentication (for users
outside the firewall). They are coming in over SSL. It uses Integrated
Authentication for internal users.
For the users who are requesting service with Basic Authentication, there is
a VB.Net client application which is using the NetworkCredential to pass the
authentication information to the web service.
However, the sequence of events that seems to always happen is:
1. client sends request
2. service responds with 401
3. client sends request again, this time including the authentication
information (user, password, domain)
So, in my IIS logs, there is a duplicate entry for each call to the web
service. The first log entry has a user value of " - " (this entry also has
the 401 code returned), and the second log entry has the correct user name.
I am certain that this is affecting overall performance of the web service.
What do I need to do in order to eliminate this "round-trip" from happening?
Thanks,
Joe
outside the firewall). They are coming in over SSL. It uses Integrated
Authentication for internal users.
For the users who are requesting service with Basic Authentication, there is
a VB.Net client application which is using the NetworkCredential to pass the
authentication information to the web service.
However, the sequence of events that seems to always happen is:
1. client sends request
2. service responds with 401
3. client sends request again, this time including the authentication
information (user, password, domain)
So, in my IIS logs, there is a duplicate entry for each call to the web
service. The first log entry has a user value of " - " (this entry also has
the 401 code returned), and the second log entry has the correct user name.
I am certain that this is affecting overall performance of the web service.
What do I need to do in order to eliminate this "round-trip" from happening?
Thanks,
Joe