Re: [Bug-wget] Connection closed vs read error

[ptrk mj]

Thanks for sheding light on it. It's important to understand what's going on.

ptrkmj

On 8/9/12, Micah Cowan  wrote:
> On 08/09/2012 12:42 AM, ptrk mj wrote:
>> Greetings everyone,
>>
>> I'd like to know what is the technical difference between
>>
>> "Connection closed at byte x."
>> and
>> "Read error at byte x/y (Connection timed out)."
>
> AIUI,
>
> "Connection closed at byte x" means that the remote end closed the
> connection while wget was still expecting to receive more data (as
> judged by Content-Length or the like). Note that in cases where the
> server doesn't tell us how much data to expect, you would never see this
> message, since in that case there's no way to know whether the server
> closed "early", or if it closed because it was properly finished sending
> content.
>
> "Read error at byte x/y (Connection timed out)." means that we simply
> stopped receiving packets from the remote server (not even a
> connection-closing packet), and the connection eventually timed out.
>
> HTH,
> -mjc
>

Re: [Bug-wget] Connection closed vs read error

[Micah Cowan]

On 08/09/2012 12:42 AM, ptrk mj wrote:
> Greetings everyone,
> 
> I'd like to know what is the technical difference between
> 
> "Connection closed at byte x."
> and
> "Read error at byte x/y (Connection timed out)."

AIUI,

"Connection closed at byte x" means that the remote end closed the
connection while wget was still expecting to receive more data (as
judged by Content-Length or the like). Note that in cases where the
server doesn't tell us how much data to expect, you would never see this
message, since in that case there's no way to know whether the server
closed "early", or if it closed because it was properly finished sending
content.

"Read error at byte x/y (Connection timed out)." means that we simply
stopped receiving packets from the remote server (not even a
connection-closing packet), and the connection eventually timed out.

HTH,
-mjc

[Bug-wget] Connection closed vs read error

[ptrk mj]

Greetings everyone,

I'd like to know what is the technical difference between

"Connection closed at byte x."
and
"Read error at byte x/y (Connection timed out)."

Please CC messages to me.

Regards
ptrkmj

[Bug-wget] wget1.14: warc.c: compilation fails due to C++ comments

[John Cornes]

Dear Maintainers,
I'd like to report a minor issue: when compiling wget 1.14 on AIX 7.1
configured with --disable-ssl, using V12.1 of IBM's XL C for AIX
compiler, compilation failed in warc.c due to the presence of C++
style comments (//):

"warc.c", line 535.3: 1506-046 (S) Syntax error.
"warc.c", line 535.24: 1506-045 (S) Undeclared identifier digest.
"warc.c", line 536.3: 1506-277 (S) Syntax error: possible missing ';' or ','?
"warc.c", line 537.49: 1506-045 (S) Undeclared identifier sha1_base32.
"warc.c", line 620.3: 1506-046 (S) Syntax error.
"warc.c", line 620.6: 1506-045 (S) Undeclared identifier RFC.
"warc.c", line 625.5: 1506-045 (S) Undeclared identifier uuid_data.
"warc.c", line 627.3: 1506-046 (S) Syntax error.
"warc.c", line 627.6: 1506-045 (S) Undeclared identifier Set.
"warc.c", line 632.49: 1506-045 (S) Undeclared identifier respectively.
make: 1254-004 The error code from the last command is 1.

warc.c:
  +535// length: "sha1:" + digest + "\0"

  +620// RFC 4122, a version 4 UUID with only random numbers

  +627// Set the four most significant bits (bits 12 through 15) of the
  +628// time_hi_and_version field to the 4-bit version number

  +631// Set the two most significant bits (bits 6 and 7) of the
  +632// clock_seq_hi_and_reserved to zero and one, respectively.

Changing to c-style comments allowed compilation to succeed.

Apologies in advance if this has already been reported.

Regards,
John

Re: [Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

[Avinash]

Ok. Thanks Petr.

On Thu, Aug 9, 2012 at 6:23 PM, Petr Pisar  wrote:

> On Thu, Aug 09, 2012 at 06:02:55PM +0530, Avinash wrote:
> > locale is UTF-8, but it was true with wget-1.10.2-0 as well.
> > If I install 'wget-1.10.2-0' RPM then SINGLE QUOTE is not replaced even
> > though locale is UTF-8.
> >
> > When I install 'wget-1.12-0'(created on top of 1.12 source) then only I
> see
> > the issue.
> >
> Than that was a bug in wget 1.10. Correct behaviour is to replace ASCII
> quotes
> to locale specific ones. en_US.UTF-8 is different from C locale by
> definition.
> If you want ASCII only output, you have to run in C locale or any other
> locale that is restricted to ASCII. en_US.UTF-8 is not such a locale.
>
> > 2012-08-09 16:24:37 (13.3 MB/s) -
> > *â*192.21.242.12:/1/Acc/index.html*â*saved
> > [8045/8045]
> >
> This looks like your terminal is not running in Unicode mode.
>
> -- Petr
>
> PS: Maybe you could be interrestd in current Fedora package
> (http://pkgs.fedoraproject.org/cgit/wget.git/tree/).
>

Re: [Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

[Jochen Roderburg]

Zitat von Petr Pisar :


On Thu, Aug 09, 2012 at 06:02:55PM +0530, Avinash wrote:

locale is UTF-8, but it was true with wget-1.10.2-0 as well.
If I install 'wget-1.10.2-0' RPM then SINGLE QUOTE is not replaced even
though locale is UTF-8.

When I install 'wget-1.12-0'(created on top of 1.12 source) then only I see
the issue.

Than that was a bug in wget 1.10. Correct behaviour is to replace  
ASCII quotes
to locale specific ones. en_US.UTF-8 is different from C locale by  
definition.


Or this particular 1.10 version was compiled without locale/language  
support.  ;-)


Regards, J.Roderburg

Re: [Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

[Petr Pisar]

On Thu, Aug 09, 2012 at 06:02:55PM +0530, Avinash wrote:
> locale is UTF-8, but it was true with wget-1.10.2-0 as well.
> If I install 'wget-1.10.2-0' RPM then SINGLE QUOTE is not replaced even
> though locale is UTF-8.
> 
> When I install 'wget-1.12-0'(created on top of 1.12 source) then only I see
> the issue.
> 
Than that was a bug in wget 1.10. Correct behaviour is to replace ASCII quotes
to locale specific ones. en_US.UTF-8 is different from C locale by definition.
If you want ASCII only output, you have to run in C locale or any other
locale that is restricted to ASCII. en_US.UTF-8 is not such a locale.

> 2012-08-09 16:24:37 (13.3 MB/s) -
> *â*192.21.242.12:/1/Acc/index.html*â *saved
> [8045/8045]
> 
This looks like your terminal is not running in Unicode mode.

-- Petr

PS: Maybe you could be interrestd in current Fedora package
(http://pkgs.fedoraproject.org/cgit/wget.git/tree/).


pgp1UaUNW7U9m.pgp
Description: PGP signature

Re: [Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

[Avinash]

locale is UTF-8, but it was true with wget-1.10.2-0 as well.
If I install 'wget-1.10.2-0' RPM then SINGLE QUOTE is not replaced even
though locale is UTF-8.

When I install 'wget-1.12-0'(created on top of 1.12 source) then only I see
the issue.

2012-08-09 16:24:37 (13.3 MB/s) -
*â*192.21.242.12:/1/Acc/index.html*â *saved
[8045/8045]

On Thu, Aug 9, 2012 at 5:30 PM, Petr Pisar  wrote:

> On Thu, Aug 09, 2012 at 04:50:46PM +0530, Avinash wrote:
> > 2) Have built a rpm on top of this source for FEDORA CORE 3
>
> Do you know this is really ancient piece of software?
>
> > 3) It get installed correctly on FC3 and wget downloads files as well
> > 4) But the output of wget shows UTF-8 value of SINGLE QUOTE instead of
> > showing SINGLE QUOTE i.e. '
> >
> [...]
> > Can somebody please help as to why it is replacing SINGLE QUOTE by its
> > UTF-8 equivalent ?
>
> What's your locale value (run command `locale')? If it is UTF-8, then you
> get
> UTF-8 characters. Try running `LC_ALL=C wget'.
>
> -- Petr
>



-- 
-Avinash

Re: [Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

[Petr Pisar]

On Thu, Aug 09, 2012 at 04:50:46PM +0530, Avinash wrote:
> 2) Have built a rpm on top of this source for FEDORA CORE 3

Do you know this is really ancient piece of software?

> 3) It get installed correctly on FC3 and wget downloads files as well
> 4) But the output of wget shows UTF-8 value of SINGLE QUOTE instead of
> showing SINGLE QUOTE i.e. '
> 
[...]
> Can somebody please help as to why it is replacing SINGLE QUOTE by its
> UTF-8 equivalent ?

What's your locale value (run command `locale')? If it is UTF-8, then you get
UTF-8 characters. Try running `LC_ALL=C wget'.

-- Petr


pgpx2pUtohCc0.pgp
Description: PGP signature

[Bug-wget] SINGLE QUOTE in wget output is replaced by UTF-8 value of SINGLE QUOTE

[Avinash]

Hi,

1) I have taken wget-1.12 source
2) Have built a rpm on top of this source for FEDORA CORE 3
3) It get installed correctly on FC3 and wget downloads files as well
4) But the output of wget shows UTF-8 value of SINGLE QUOTE instead of
showing SINGLE QUOTE i.e. '

It shows

2012-08-09 16:24:37 (13.3 MB/s) - *â*192.21.242.12:/1/Acc/index.html*â*

instead of

2012-08-09 16:24:37 (13.3 MB/s) - '**192.21.242.12:/1/Acc/index.html'

Hexedit shows those characters as 0xE2 0x80 0x9C and 0xE2 0x80 0x9D instead
of 0x27

Can somebody please help as to why it is replacing SINGLE QUOTE by its
UTF-8 equivalent ?