Aubrey Li wrote:
On Thu, Apr 9, 2009 at 2:10 AM, Shawn Walker <> wrote:
Aubrey Li wrote:
On Thu, Apr 9, 2009 at 2:04 AM, Shawn Walker <> wrote:
Aubrey Li wrote:
$ pkg publisher dev
Publisher: dev
Alias: None
Origin URI: http://pkg.opensolaris.org/dev/
SSL Key: None
SSL Cert: None
Client UUID: fd180194-11d6-11de-81cf-0015172d2644
Catalog Updated: Fri Mar 20 12:02:18 2009
Enabled: Yes
Okay, here's something interesting to try:
wget -O /dev/null -S http://pkg.opensolaris.org/dev/catalog/0
What's the output from that?
(You can cancel the download once it prints the headers.)
Cheers,
--
Shawn Walker
$ wget -O /dev/null -S http://pkg.opensolaris.org/dev/catalog/0
--03:09:12-- http://pkg.opensolaris.org/dev/catalog/0
=> `/dev/null'
Resolving proxy01.xx.xxxxx.com... 172.16.99.134, 172.16.99.133
Connecting to proxy01.xx.xxxxx.com|172.16.99.134|:911... connected.
Proxy request sent, awaiting response...
HTTP/1.1 200 OK
Date: Wed, 08 Apr 2009 18:05:23 GMT
Server: CherryPy/3.1.1
Last-Modified: 2009-03-31T02:34:59.962655
X-Catalog-Type: full
Content-Type: text/plain;charset=utf-8
Via: 1.1 pddmzpr02.xx.xxxxx.com
Content-Length: 1883337
Connection: close
Age: 0
Ah, okay. So you are going through a proxy.
Is this a problem? It works properly when I upgraded 109->110 on the same box.
We've had several reports of proxy users or users with ISPs that do deep
packet inspection traffic shaping experiencing issues.
What's interesting here is that wget seems to work fine, but the usage
pattern of the pkg client itself seems to not allow the transaction to
work as expected.
--
Shawn Walker
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
