[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://'
From: |
Wilfred van Velzen |
Subject: |
Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://' |
Date: |
Fri, 16 Mar 2012 00:33:49 +0100 |
On Thu, Mar 15, 2012 at 11:34 PM, Giuseppe Scrivano <address@hidden> wrote:
>>> can you please provide more information? Where do you get that message?
>>
>> Everywhere, for example:
>>
>>> wget http://google.com
>> asking libproxy about url 'http://google.com/'
>> libproxy suggest to use 'direct://'
>> ...
>>
>> It seems to be the first two lines of output that wget always prints.
>
> What happens if you specify --no-proxy?
> wget --no-proxy http://google.com
--2012-03-16 00:24:17-- http://google.com/
Resolving google.com (google.com)... 2a00:1450:400c:c01::64,
173.194.67.113, 173.194.67.100, ...
Connecting to google.com (google.com)|2a00:1450:400c:c01::64|:80... connected.
...
So those 2 lines are now gone...
> Can you please attach the output you get if you pass -d (this time
> without --no-proxy)?
I don't think it gives much more information about the issue, but here it is:
> wget -d http://google.com
DEBUG output created by Wget on linux-gnu.
URI encoding = `UTF-8'
asking libproxy about url 'http://google.com/'
libproxy suggest to use 'direct://'
--2012-03-16 00:24:46-- http://google.com/
Resolving google.com (google.com)... 2a00:1450:400c:c01::64,
173.194.67.113, 173.194.67.100, ...
Caching google.com => 2a00:1450:400c:c01::64 173.194.67.113
173.194.67.100 173.194.67.138 173.194.67.101 173.194.67.102
173.194.67.139
Connecting to google.com (google.com)|2a00:1450:400c:c01::64|:80... connected.
Created socket 4.
Releasing 0x0000000000688090 (new refcount 1).
---request begin---
GET / HTTP/1.1
User-Agent: Wget/ (linux-gnu)
Accept: */*
Host: google.com
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 301 Moved Permanently
Location: http://www.google.com/
Content-Type: text/html; charset=UTF-8
Date: Thu, 15 Mar 2012 23:24:46 GMT
Expires: Sat, 14 Apr 2012 23:24:46 GMT
Cache-Control: public, max-age=2592000
Server: gws
Content-Length: 219
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
---response end---
301 Moved Permanently
Registered socket 4 for persistent reuse.
URI content encoding = `UTF-8'
Location: http://www.google.com/ [following]
Skipping 219 bytes of body: [<HTML><HEAD><meta
http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>301 Moved</TITLE></HEAD><BODY>
<H1>301 Moved</H1>
The document has moved
<A HREF="http://www.google.com/">here</A>.
</BODY></HTML>
] done.
URI content encoding = None
asking libproxy about url 'http://www.google.com/'
libproxy suggest to use 'direct://'
--2012-03-16 00:24:46-- http://www.google.com/
conaddr is: 2a00:1450:400c:c01::64
Resolving www.google.com (www.google.com)... 2a00:1450:400c:c01::93,
173.194.78.147, 173.194.78.104, ...
Caching www.google.com => 2a00:1450:400c:c01::93 173.194.78.147
173.194.78.104 173.194.78.103 173.194.78.105 173.194.78.106
173.194.78.99
Releasing 0x0000000000692470 (new refcount 1).
Found www.google.com in host_name_addresses_map (0x692470)
Connecting to www.google.com
(www.google.com)|2a00:1450:400c:c01::93|:80... connected.
Created socket 6.
Releasing 0x0000000000692470 (new refcount 1).
---request begin---
GET / HTTP/1.1
User-Agent: Wget/ (linux-gnu)
Accept: */*
Host: www.google.com
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 302 Found
Location: http://www.google.nl/
Cache-Control: private
Content-Type: text/html; charset=UTF-8
Set-Cookie:
PREF=ID=d810aacf341facd7:FF=0:TM=1331853886:LM=1331853886:S=fNUTwgXnnv2Pv5Zn;
expires=Sat, 15-Mar-2014 23:24:46 GMT; path=/; domain=.google.com
Set-Cookie:
NID=57=f5XV6XxtrZrCGixHDOp97J37NrTAa_xgpM6anAtiWbZQJaLv9j5-IG2zlnIt5N7GA0HLBCYu75p5oyknYyIrGW_r3XoXhoofMtfAWecEqBsYu5niT9hHwUapWA8ShuIR;
expires=Fri, 14-Sep-2012 23:24:46 GMT; path=/; domain=.google.com;
HttpOnly
P3P: CP="This is not a P3P policy! See
http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657
for more info."
Date: Thu, 15 Mar 2012 23:24:46 GMT
Server: gws
Content-Length: 218
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
---response end---
302 Found
cdm: 1 2 3 4 5 6 7 8
Stored cookie google.com -1 (ANY) / <permanent> <insecure> [expiry
2014-03-16 00:24:46] PREF
ID=d810aacf341facd7:FF=0:TM=1331853886:LM=1331853886:S=fNUTwgXnnv2Pv5Zn
cdm: 1 2 3 4 5 6 7 8
Stored cookie google.com -1 (ANY) / <permanent> <insecure> [expiry
2012-09-15 01:24:46] NID
57=f5XV6XxtrZrCGixHDOp97J37NrTAa_xgpM6anAtiWbZQJaLv9j5-IG2zlnIt5N7GA0HLBCYu75p5oyknYyIrGW_r3XoXhoofMtfAWecEqBsYu5niT9hHwUapWA8ShuIR
Disabling further reuse of socket 4.
Closed fd 4
Registered socket 6 for persistent reuse.
URI content encoding = `UTF-8'
Location: http://www.google.nl/ [following]
Skipping 218 bytes of body: [<HTML><HEAD><meta
http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="http://www.google.nl/">here</A>.
</BODY></HTML>
] done.
URI content encoding = None
asking libproxy about url 'http://www.google.nl/'
libproxy suggest to use 'direct://'
--2012-03-16 00:24:46-- http://www.google.nl/
conaddr is: 2a00:1450:400c:c01::93
Resolving www.google.nl (www.google.nl)... 2a00:1450:400c:c01::5e, 173.194.67.94
Caching www.google.nl => 2a00:1450:400c:c01::5e 173.194.67.94
Releasing 0x00000000006966b0 (new refcount 1).
Found www.google.nl in host_name_addresses_map (0x6966b0)
Connecting to www.google.nl
(www.google.nl)|2a00:1450:400c:c01::5e|:80... connected.
Created socket 7.
Releasing 0x00000000006966b0 (new refcount 1).
---request begin---
GET / HTTP/1.1
User-Agent: Wget/ (linux-gnu)
Accept: */*
Host: www.google.nl
Connection: Keep-Alive
---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Date: Thu, 15 Mar 2012 23:24:46 GMT
Expires: -1
Cache-Control: private, max-age=0
Content-Type: text/html; charset=ISO-8859-1
Set-Cookie:
PREF=ID=ca066f15d0fc78a9:FF=0:TM=1331853886:LM=1331853886:S=MmFaDh7f-lDe9YaJ;
expires=Sat, 15-Mar-2014 23:24:46 GMT; path=/; domain=.google.nl
Set-Cookie:
NID=57=IUH6oCVD6SILWCwCFkTxuQr-yOxA48bQeBKPRR11kuPyIo9jMM74XSOkB5cT--NvaiK7_j01Wd2lCQWZPxmCi7K3gV2Gr-ck-doNf5wJMMAfewgaX5JtfwqdNvK47-ef;
expires=Fri, 14-Sep-2012 23:24:46 GMT; path=/; domain=.google.nl;
HttpOnly
P3P: CP="This is not a P3P policy! See
http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=151657
for more info."
Server: gws
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Transfer-Encoding: chunked
---response end---
200 OK
cdm: 1 2 3 4 5 6 7 8
Stored cookie google.nl -1 (ANY) / <permanent> <insecure> [expiry
2014-03-16 00:24:46] PREF
ID=ca066f15d0fc78a9:FF=0:TM=1331853886:LM=1331853886:S=MmFaDh7f-lDe9YaJ
cdm: 1 2 3 4 5 6 7 8
Stored cookie google.nl -1 (ANY) / <permanent> <insecure> [expiry
2012-09-15 01:24:46] NID
57=IUH6oCVD6SILWCwCFkTxuQr-yOxA48bQeBKPRR11kuPyIo9jMM74XSOkB5cT--NvaiK7_j01Wd2lCQWZPxmCi7K3gV2Gr-ck-doNf5wJMMAfewgaX5JtfwqdNvK47-ef
Disabling further reuse of socket 6.
Closed fd 6
Registered socket 7 for persistent reuse.
URI content encoding = `ISO-8859-1'
Length: unspecified [text/html]
Saving to: `index.html.4'
[ <=>
] 11,112
--.-K/s in 0.03s
2012-03-16 00:24:46 (335 KB/s) - `index.html.4' saved [11112]
--
Met vriendelijke groet / Best regards,
Wilfred van Velzen
- [Bug-wget] wget reports: libproxy suggest to use 'direct://', Wilfred van Velzen, 2012/03/15
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Giuseppe Scrivano, 2012/03/15
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Wilfred van Velzen, 2012/03/16
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Giuseppe Scrivano, 2012/03/17
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Wilfred van Velzen, 2012/03/17
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Giuseppe Scrivano, 2012/03/17
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Wilfred van Velzen, 2012/03/19
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Ángel González, 2012/03/20
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Wilfred van Velzen, 2012/03/21
- Re: [Bug-wget] wget reports: libproxy suggest to use 'direct://', Wilfred van Velzen, 2012/03/21