Bug 174397

Summary: YOU fails when using authenticated proxy session
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Roy Kimbrell <roy.kimbrell>
Component: YOUAssignee: Martin Vidner <mvidner>
Status: RESOLVED WONTFIX QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: jsuchome, roy.kimbrell, suse-beta, thomas.anders
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: proxy details from /etc/sysconfig
/root/.curlrc

Description Roy Kimbrell 2006-05-10 15:07:22 UTC
I installed SuSE 10 on a laptop while connected directly to the Internet.
At this time, YOU updated the installation.  I moved the laptop to my
office which is behind a proxy that uses authentication - userID &
password.  Using YaST>Network Services>Proxy, I updated the proxy
configuration.  

When testing SuSEWatcher I got "Failed Connection" repeatedly - after
trying lots of things, including adding "/" at the end of the proxy in the
configuration file, copying .curlrc from /root to the local directory,
adding ":80" (the proxy port) at the end of the proxy URL in the
configuration file.  

The URL (see below) that YOU is attempting to reach returns a list of
servers in a browser with the same proxy configuration settings.  That is, with the same proxy settings, the browser works fine.

When looking again at YaST>Network Services>Proxy, (I was adding a "/" at the end of each of the proxy URLs had no effect) and clicked the "Test Proxy Settings" button.  I got the folling error:

------------------------------------------------------

* About to connect() to httpe1.northgrum.com port 80
*   Trying 208.20.220.69... connected
* Connected to httpe1.northgrum.com (208.20.220.69) port 80
* Establish HTTP proxy tunnel to secure-www.novell.com:443
* Proxy auth using Basic with user 'kimbrro'
> CONNECT secure-www.novell.com:443 HTTP/1.0
> Host: secure-www.novell.com:443
> Proxy-Authorization: Basic a2ltYnJybzpzeXp5Z3k2Xg==
> User-Agent: curl/7.14.0 (i686-suse-linux) libcurl/7.14.0 OpenSSL/0.9.7g
zlib/1.2.3
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 302 
< Proxy-agent: iPlanet-Web-Proxy-Server/3.6-SP6
< Date: Mon, 01 May 2006 19:42:13 GMT
< Connection: close
< Location:
http://208.20.220.77:15871/cgi-bin/authenticate.cgi?ws-session=2082699104
< Content-type: text/html
< Content-length: 249
< Connection: keep-alive
< Proxy-connection: keep-alive
< 
* Received HTTP code 302 from proxy after CONNECT
* Closing connection #0

curl: (56) Received HTTP code 302 from proxy after CONNECT

---------------------------------

Note that there was a connection to the proxy server; however, subsequent
to that there was an error.  I guess this is the problem getting YOU to
download patches.   

To repeat the problem, try updating SuSE via an authenticating proxy.



The YOU URL is

URL: http://www.suse.de/cgi-bin/suseservers.cgi
URL:
http://www.suse.de/cgi-bin/suseservers.cgi?product=SUSE%20LINUX&version=10.0&basearch=i386&arch=i686〈=en_US&business=0&check=0&distproduct=SuSE-Linux-DVD-10.0-0&yast2-online-update=2.12.4-2&yast2-packagemanager=2.12.21-0.1&liby2util=2.12.9-0.4&timezone=US/Central&machid=b69dd3c81a1996de9b
Comment 1 Jiří Suchomel 2006-05-11 13:27:32 UTC
This more looks like an error in proxy configuration...
Comment 2 Martin Vidner 2006-05-11 16:47:54 UTC
Which version of yast2-network and aaa_base do you have?
What is in your /etc/sysconfig/proxy and /root/.curlrc ? (censor the passwords)

(302 is Moved Temporarily)
Comment 3 Roy Kimbrell 2006-05-12 13:01:26 UTC
I'm out of my office and I've modified the proxy information to update the system. I'll be there Monday and will modify the proxy info again and make sure the same problem occurs then.  I'll let you know what happens.  The current contents of /etc/sysconfig/proxy are at the end of the message.  The only difference seems to be that PROXY_ENABLED="no" instead of "yes".  The rest of the proxy information is as it was during the problem.  As I said, Monday, I'll change it again and verify that the problem still occurs and let you know what happens.

 I had copied /root/.curlrc into my local directory when the problem was occuring.  This is the contents:

# Changed by YaST2 module proxy 05/01/2006
proxy-user = "kimbrro:syzygy6^"

I just checked /root/.curlrc - the contents have not changed.


yast2-network version  is 2.12.15-2-i586
aaa_base version is 10.0-28


Contents of /etc/sysconfig/proxy

## Path:        Network/Proxy
## Description:
## Type:        yesno
## Default:     no
## Config:      kde,profiles
#
# Enable a generation of the proxy settings to the profile.
# This setting allows to turn the proxy on and off while
# preserving the particular proxy setup.
#
PROXY_ENABLED="no"

## Type:        string
## Default:     ""
#
# Some programs (e.g. lynx, arena and wget) support proxies, if set in
# the environment.  SuSEconfig can add these environment variables to
# /etc/SuSEconfig/* (sourced by /etc/profile etc.) -
# See http://portal.suse.com/sdb/en/1998/01/lynx_proxy.html for more details.
# Example: HTTP_PROXY="http://proxy.provider.de:3128/"
HTTP_PROXY="http://httpe1.northgrum.com:80"

## Type:        string
## Default:     ""
#
# Some programs (e.g. lynx, arena and wget) support proxies, if set in
# the environment.  SuSEconfig can add these environment variables to
# /etc/SuSEconfig/* (sourced by /etc/profile etc.) -
# this setting is for https connections
HTTPS_PROXY="http://httpe1.northgrum.com:80"

## Type:        string
## Default:     ""
#
# Example: FTP_PROXY="http://proxy.provider.de:3128/"
#
FTP_PROXY="http://httpe1.northgrum.com:80"

## Type:        string
## Default:     ""
#
# Example: GOPHER_PROXY="http://proxy.provider.de:3128/"
#
GOPHER_PROXY=""

## Type:        string(localhost)
## Default:     localhost
#
# Example: NO_PROXY="www.me.de, do.main, localhost"
#
NO_PROXY="localhost, northgrum.com"
Comment 4 Roy Kimbrell 2006-05-16 14:37:44 UTC
Created attachment 83645 [details]
proxy details from /etc/sysconfig
Comment 5 Roy Kimbrell 2006-05-16 14:39:09 UTC
Created attachment 83648 [details]
/root/.curlrc
Comment 6 Roy Kimbrell 2006-05-16 14:41:10 UTC
Okay it's Tuesday - sorry, I promised Monday I'd do this.

I changed the proxy settings via Yast and clicked "Test Proxy Settings".  The test failed with the following complaint:

----------------------------------

* About to connect() to httpe1.northgrum.com port 80
*   Trying 208.20.220.69... connected
* Connected to httpe1.northgrum.com (208.20.220.69) port 80
* Establish HTTP proxy tunnel to secure-www.novell.com:443
* Proxy auth using Basic with user 'kimbrro'
> CONNECT secure-www.novell.com:443 HTTP/1.0
> Host: secure-www.novell.com:443
> Proxy-Authorization: Basic a2ltYnJybzpzeXp5Z3k2Xg==
> User-Agent: curl/7.14.0 (i686-suse-linux) libcurl/7.14.0 OpenSSL/0.9.7g zlib/1.2.3
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 302 
< Proxy-agent: iPlanet-Web-Proxy-Server/3.6-SP6
< Date: Tue, 16 May 2006 14:28:54 GMT
< Connection: close
< Location: http://208.20.220.77:15871/cgi-bin/authenticate.cgi?ws-session=2054078665
< Content-type: text/html
< Content-length: 249
< Connection: keep-alive
< Proxy-connection: keep-alive
< 
* Received HTTP code 302 from proxy after CONNECT
* Closing connection #0

curl: (56) Received HTTP code 302 from proxy after CONNECT

--------------------------

http://httpe1.northgrum.com:80 is the correct proxy.  It's the one I use in Firefox which works fine.  The user id and password are also correct.  I retyped the password and tried it again.

Attached are the 
Comment 7 Roy Kimbrell 2006-05-16 14:51:47 UTC
Just noticed that the "PROXY_ENABLED" value in the /etc/sysconfig/proxy I attached is set to "no".  I clicked "Finish" in Yast and it turned to "yes."  I've attached the new file.  In Yast, I reopened the Proxy settings page and clicked the test button again with the same results.  I also tried Online Update.  It complained: "Warning  Cannot fetch remote server list.  Only user-defined patch sources will be available.  Possuble solution:  Check network connection"

Copying the URLs in the Details of the Warning into Firefox, I get lists of servers.

The URLs are

http://www.suse.de/cgi-bin/suseservers.cgi

and 

http://www.suse.de/cgi-bin/suseservers.cgi?product=SUSE%20LINUX&version=10.0&basearch=i386&arch=i686&lang=en_US&business=0&check=0&distproduct=SuSE-Linux-DVD-10.0-0&yast2-online-update=2.12.4-2&yast2-packagemanager=2.12.21-0.1&liby2util=2.12.9-0.4&timezone=US/Central&machid=b69dd3c81a1996de9b
Comment 8 Roy Kimbrell 2006-05-16 15:15:15 UTC
I tried a curl connection to the two URLs (individually).  The results are below.  Don't know what they mean exactly since I don't know much about curl.

-----First attempt-------------

$curl -U kimbrro:syzygy6^ -v -x httpe1.northgrum.com:80 http://www.suse.de/cgi-bin/suseservers.cgi
* About to connect() to httpe1.northgrum.com port 80
*   Trying 208.20.220.69... connected
* Connected to httpe1.northgrum.com (208.20.220.69) port 80
* Proxy auth using Basic with user 'kimbrro'
> GET http://www.suse.de/cgi-bin/suseservers.cgi HTTP/1.1
> Proxy-Authorization: Basic a2ltYnJybzpzeXp5Z3k2Xg==
> User-Agent: curl/7.14.0 (i686-suse-linux) libcurl/7.14.0 OpenSSL/0.9.7g zlib/1.2.3
> Host: www.suse.de
> Pragma: no-cache
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 302
< Proxy-agent: iPlanet-Web-Proxy-Server/3.6-SP6
< Date: Tue, 16 May 2006 15:03:10 GMT
< Connection: close
< Location: http://208.20.220.77:15871/cgi-bin/authenticate.cgi?ws-session=2490308767
< Content-type: text/html
< Content-length: 249
< Connection: keep-alive
< Proxy-connection: keep-alive
<HTML><HEAD><TITLE></TITLE></HEAD><BODY><H1></H1>
Closing connection #0
This document has moved to a new <a href="http://208.20.220.77:15871/cgi-bin/authenticate.cgi?ws-session=2490308767">location</a>. Please update your docum 

---------End of first attempt ---------------

---------Second attempt----------------------

 curl -U kimbrro:syzygy6^ -v -x httpe1.northgrum.com:80 http://www.suse.de/cgi-bin/suseservers.cgi?product=SUSE%20LINUX&version=10.0&basearch=i386&arch=i686&lang=en_US&business=0&check=0&distproduct=SuSE-Linux-DVD-10.0-0&yast2-online-update=2.12.4-2&yast2-packagemanager=2.12.21-0.1&liby2util=2.12.9-0.4&timezone=US/Central&machid=b69dd3c81a1996de9b
[1] 10575
[2] 10576
[3] 10577
[4] 10578
[5] 10579
[6] 10580
[7] 10581
[8] 10582
bash: yast2-online-update=2.12.4-2: command not found
[9] 10583
bash: yast2-packagemanager=2.12.21-0.1: command not found
[10] 10584
[11] 10585
[12] 10586
[2]   Done                    version=10.0
[3]   Done                    basearch=i386
[4]   Done                    arch=i686
[5]   Done                    lang=en_US
[6]   Done                    business=0
[7]   Done                    check=0
[8]   Done                    distproduct=SuSE-Linux-DVD-10.0-0
[9]   Exit 127                yast2-online-update=2.12.4-2
[10]   Exit 127                yast2-packagemanager=2.12.21-0.1
[11]   Done                    liby2util=2.12.9-0.4
[12]   Done                    timezone=US/Central
* About to connect() to httpe1.northgrum.com port 80
*   Trying 208.20.220.69... rek@Gazelle:~> connected
* Connected to httpe1.northgrum.com (208.20.220.69) port 80
* Proxy auth using Basic with user 'kimbrro'
> GET http://www.suse.de/cgi-bin/suseservers.cgi?product=SUSE%20LINUX HTTP/1.1
> Proxy-Authorization: Basic a2ltYnJybzpzeXp5Z3k2Xg==
> User-Agent: curl/7.14.0 (i686-suse-linux) libcurl/7.14.0 OpenSSL/0.9.7g zlib/1.2.3
> Host: www.suse.de
> Pragma: no-cache
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 302
< Proxy-agent: iPlanet-Web-Proxy-Server/3.6-SP6
< Date: Tue, 16 May 2006 15:10:55 GMT
< Connection: close
< Location: http://208.20.220.77:15871/cgi-bin/authenticate.cgi?ws-session=2876188857
< Content-type: text/html
< Content-length: 249
< Connection: keep-alive
< Proxy-connection: keep-alive
<HTML><HEAD><TITLE></TITLE></HEAD><BODY><H1></H1>
Closing connection #0
This document has moved to a new <a href="http://208.20.220.77:15871/cgi-bin/authenticate.cgi?ws-session=2876188857">location</a>. Please update your documents and hotlists accordingly.</BODY></HTML>

-------------End of Second attempt-----------------
Comment 9 Michael Gross 2006-06-13 11:28:11 UTC
*** Bug 183977 has been marked as a duplicate of this bug. ***
Comment 10 Christian Boltz 2006-06-13 13:01:59 UTC
updating version according to bug 183977
Comment 11 Martin Vidner 2006-09-21 14:56:09 UTC
No, that was a different problem.

We have rewritten the package management component for 10.1 so we are reluctant to fix problems in an unmaintained version. Please try if the problem is still present in 10.1 or even in an alpha version of 10.2. See http://en.opensuse.org/Download
Comment 12 Matej Horvath 2007-02-16 14:25:15 UTC
No reaction on this bug for a long time. Closing as CANTFIX.