HTTPS and Proxy Authentication Issue.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

Has any one else experienced a issue with HTTPS and
Proxy that requires authentication for external access ?

Initial requests, where the user hasn't already authenticated,
seem to return a "400 Bad Request" Error.

Packet traces using ethereal show that IE upon receiving
the proxy authorisation response from the proxy server
prompts the user for the authentication details, but
sends the incorrect response to the proxy server.

In more detail, the sequence of events from a network packet
traces point of view is:
1) IE Sends a CONNECT <website>:443
2) The proxy responds with HTTP Error 407 - Proxy Authorisation Required.
3) IE prompts the user for the authentication credentials.
4) IE then sends a GET /<url> request to the proxy (without the
authentication details)
5) The proxy then resposds (correctly) with a 400 Bad Reqeust Error.
<click on refresh>
6) IE sends a CONNECT <website> + the authentication credentials.

Other browsers (eg. Mozilla) at Step 4, send a request with
CONNECT <websiteurl>:443 + the authentication details
and the https page downloads correctly.
 
Brad said:
Hi,

Has any one else experienced a issue with HTTPS and
Proxy that requires authentication for external access ?
Click to expand...

Apparently --

http://groups-beta.google.com/group...ication+407+explorer&rnum=10#97a6d34e6724ecac

(Google Groups search for
proxy authentication 407 explorer
)

<quote>
IE makes another anonymous connection attempt.
Apparently, just to be sure that this is not an error
and proxy *really* needs user authentication ;-)
Initial requests, where the user hasn't already authenticated,
seem to return a "400 Bad Request" Error.
Click to expand...

The only unstated factor that I can think of is your security setting
User Authentication Logon
The default is
Automatic logon only in the intranet zone
Is your script in that zone? Does one of the other settings
work any differently?


Hmm... see if the workaround described here applies
(Courtesy Henri Leboeuf)

<title>KB312176 - Heavy NTLM authentication traffic occurs between
Internet Explorer and the proxy server</title>

http://groups-beta.google.com/group...er++group:microsoft.*&rnum=1#d85518819d5b0e5e

(Google Groups search for
proxy authentication 407 explorer group:microsoft.*
)

<quote>
set the MaxConnectionsPerServer value to 1.
This limits the number of simultaneous HTTP connection to one.
The default value is to use two connections.
</quote>


HTH

Robert Aldwinckle
---
 
Back
Top