[Mono-bugs] [Bug 77405][Nor] Changed - incorrect http_proxy handling

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by colin at univ-metz.fr.

http://bugzilla.ximian.com/show_bug.cgi?id=77405

--- shadow/77405	2006-01-31 14:11:55.000000000 -0500
+++ shadow/77405.tmp.19418	2006-01-31 18:38:18.000000000 -0500
@@ -71,6 +71,28 @@
 It is fine that Lynx has those features, but we need more than that,
 and that page has no information on the specific subject we are discussing
 
 ------- Additional Comments From james at ximian.com  2006-01-31 14:11 -------
 Hmmm, it seems this is not really fixable, as the proxy API doesn't
 appear to differentiate between http and https traffic.
+
+------- Additional Comments From colin at univ-metz.fr  2006-01-31 18:38 -------
+it seams to have differences between unix and .Net.
+Unix uses http_proxy and https_proxy environments variables to set
+proxy, that lets choice in different proxy for each protocol. .Net
+allow one proxy for both.
+For example if http://proxy.com:3128 is set as proxy and you request
+https://foo.com
+WebRequest send the HttpRequest via Http(80) to the proxy and say in
+request it would like to join(CONNECT) foo.com via https, proxy then
+initiate https connection.
+(https)http---->------>----http(proxy)https---->---->https://foo.com
+I think that in your case you have a connection failure because the
+address you specify in http_proxy is not a proxy (or https is not
+allowed ?).
+I do some test with SQUID as proxy and all seams to work fine.
+i hope it's clear :(
+
+
+
+
+