[pca] back and annoyed

[Don O'Malley]

Hi Martin,

Works for me...

bash-3.00# /usr/sfw/bin/wget --no-check-certificate --http-user="xxxxxxxx" --http-passwd="xxxxxxx" "https://sunsolve.sun.com/patchdiag.xref" -O /tmp/patchdiag.xref
--11:26:46--  https://sunsolve.sun.com/patchdiag.xref
           => `/tmp/patchdiag.xref'
Resolving sunsolve.sun.com... 192.18.108.40
Connecting to sunsolve.sun.com|192.18.108.40|:443... connected.
WARNING: Certificate verification error for sunsolve.sun.com: self signed certificate in certificate chain
HTTP request sent, awaiting response... 200 OK
Length: 3,059,271 (2.9M) [text/plain]

100%[====================================>] 3,059,271    177.24K/s    ETA 00:00

11:27:01 (221.69 KB/s) - `/tmp/patchdiag.xref' saved [3059271/3059271]

bash-3.00#


It is worth noting that the patchdiag.xref file is still hosted on 
SunSolve and not akamai (which is the case for all patches).
Hence, the output for a wget for a patch will look very different (with 
redirects to/from getupdates2.sun.com & a248.e.akamai.net:

bash-3.00# /usr/sfw/bin/wget --no-check-certificate --http-user="xxxxxxxxxx" --http-passwd="xxxxxxxxx" "http://sunsolve.sun.com/pdownload.do?target=120068-02&method=h" -O /tmp/120068-02.zip
--11:32:35--  http://sunsolve.sun.com/pdownload.do?target=120068-02&method=h
           => `/tmp/120068-02.zip'
Resolving sunsolve.sun.com... 192.18.108.40
Connecting to sunsolve.sun.com|192.18.108.40|:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://getupdates2.sun.com/all_unsigned/120068-02.zip [following]
--11:32:36--  https://getupdates2.sun.com/all_unsigned/120068-02.zip
           => `/tmp/120068-02.zip'
Resolving getupdates2.sun.com... 198.232.168.157
Connecting to getupdates2.sun.com|198.232.168.157|:443... connected.
WARNING: Certificate verification error for getupdates2.sun.com: self signed certificate in certificate chain
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://a248.e.akamai.net/f/248/21808/15m/sun.download.akamai.com/21808/patches/patchroot/all_unsigned/120068-02.zip?AuthParam=1250505272_53071ddfcae92392c1e4ff464918b928&TUrl=L0QdUQV8Z4i0fdED3QTP3SJDWA8FMyaJsHfIWf4X29kTWQpKEzIbwqFuyRPZ&TicketId=3q32lluBNxBR&GroupName=SWUP&BHost=sdlc6g.sun.com&FilePath=/patches/patchroot/all_unsigned/120068-02.zip&File=120068-02.zip [following]
--11:32:40--  https://a248.e.akamai.net/f/248/21808/15m/sun.download.akamai.com/21808/patches/patchroot/all_unsigned/120068-02.zip?AuthParam=1250505272_53071ddfcae92392c1e4ff464918b928&TUrl=L0QdUQV8Z4i0fdED3QTP3SJDWA8FMyaJsHfIWf4X29kTWQpKEzIbwqFuyRPZ&TicketId=3q32lluBNxBR&GroupName=SWUP&BHost=sdlc6g.sun.com&FilePath=/patches/patchroot/all_unsigned/120068-02.zip&File=120068-02.zip
           => `/tmp/120068-02.zip'
Resolving a248.e.akamai.net... 92.122.126.147, 92.122.126.162
Connecting to a248.e.akamai.net|92.122.126.147|:443... connected.
WARNING: Certificate verification error for a248.e.akamai.net: unable to get local issuer certificate
HTTP request sent, awaiting response... 200 OK
Length: 47,267 (46K) [application/zip]

100%[====================================>] 47,267       140.88K/s             

11:32:41 (140.57 KB/s) - `/tmp/120068-02.zip' saved [47267/47267]

bash-3.00# 


I have been trying to gather a list of problems with wget patch access 
since the change to using the new download service.
http://sunsolve.sun.com/search/document.do?assetkey=1-9-240066-1 was 
updated last Friday to reflect this information.

My understanding was that the move to the new download service would be 
transparent, so I was hoping to confirm that everything was stable prior 
to publicizing it.
Unfortunately, this is obviously not the case.

I have confirmed that the download service has been working correctly 
for the past hour (though there appears to have been an issue prior to 
that affecting some downloads).

Can you let me know if you are still having issues?

Best,
-Don
Martin Paul wrote:
> Hi,
>
> I'm back from vacation, catching up on my e-mail. I see that in (good) 
> old tradition once again a change to SunSolve broke pca. One thing is 
> that support for HTTP seems to have been cancelled without previous 
> announcement.
>
> Plus, right now, I can't even download patchdiag.xref. Any request to 
> https://sunsolve.sun.com/patchdiag.xref gets stuck at:
>
> Resolving sunsolve.sun.com... 192.18.108.40
> Connecting to sunsolve.sun.com|192.18.108.40|:443... connected.
> ^C
>
> Using HTTP instead - which shouldn't be allowed on SunSolve anymore - 
> seems to work. I will need to look into this mess.
>
> Martin.
>