bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: uploading error - Closed 4/SSL 0x022ed8d8


From: Tim Rühsen
Subject: Re: uploading error - Closed 4/SSL 0x022ed8d8
Date: Fri, 1 Nov 2019 09:45:51 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0

Hi Jiri,

that was a good test.

It moves the issue to your windows boxes. You should now find out the
difference between the wget on imac and on windows (wget version and
type+version of the TLS library).

We (as the GNU Wget project) do not support Windows directly.

The "inofficial" binaries for windows can be found at
https://eternallybored.org/misc/wget/

Try different versions to see if the problem persists.

Also, I move this discussion back to bug-wget ML, since there are also
some windows users who might help.

Regards, Tim

On 01.11.19 09:31, Jiří Šír wrote:
> Hello Tim,
> thank you very much for answer.
> 
> I have tried install wget on iMac machine and here is everything ok with
> the „big“ XML file.
> This machine is connect to the same network as Windows machine where the
> problem is.
> 
> I think it is not server problem.
> 
> I attached some pcap files.
> 
> I do not understand „without changing your credentials afterwards“ so I
> attached one pcap file with bad authorization.
> 
> Thank you.
> Kind regards.
> 
> Jiří Šír
> 
> +420 223 016 569
> Cyklo 69 s.r.o.
> Specialized Concept Store
> Jug. partyzánů 6, Praha 6
> www.cyklo69.cz <https://www.cyklo69.cz>
> 
> 
> 
> 
> 
> 
> 
>> 31. 10. 2019 v 19:08, Tim Rühsen <address@hidden
>> <mailto:address@hidden>>:
>>
>> Hello Jiří,
>>
>> the connection is definitely closed from the server side. (Of course it
>> could be some middle box as well).
>>
>> If you open your pcap file in wireshark, there is packet #86 where
>> 104.17.52.5 sent a FIN, ACK to your local machine. We just can see *why*
>> this has been done. Possibly the server doesn't like something (it could
>> nearly be anything).
>>
>> Maybe the IT man can see more on his side.
>>
>> If you try the same command from a linux box, possibly with a different
>> OpenSSL version (or even wget built with GnuTLS) and you see the same
>> issue - then it's definitely the server or a middle box.
>> Having a pcap with a http request would definitely allow more insight -
>> but don't make one up without changing your credentials afterwards !
>>
>> Sorry, that's all I can say.
>>
>> Regards, Tim
>> --
>> Consider sponsoring: https://github.com/sponsors/rockdaboot
>>
>>
>> On 31.10.19 18:31, Jiří Šír wrote:
>>> Hello Tim,
>>> thank you very much for your answer.
>>>
>>> The Authorization is ok, it is comfirmed by IT man from server side.
>>>
>>>  "--secure-protocol=TLSv1_2" unfortunately is not working too, the
>>> result is the same.
>>>
>>> I have attached some snapshot from wireshark. I hope it will help
>>> somehow.
>>>
>>> Thank you.
>>>
>>> Kind Regards.
>>>
>>> Jiří Šír
>>>
>>> +420 223 016 569
>>> Cyklo 69 s.r.o.
>>> Specialized Concept Store
>>> Jug. partyzánů 6, Praha 6
>>> www.cyklo69.cz <http://www.cyklo69.cz/> <http://www.cyklo69.cz
>>> <http://www.cyklo69.cz/>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>> 31. 10. 2019 v 9:47, Tim Rühsen <address@hidden
>>>> <mailto:address@hidden>
>>>> <mailto:address@hidden>>:
>>>>
>>>> Hi Jiri,
>>>>
>>>> that means a write error happened.
>>>>
>>>> The reason for this is unclear due to missing information.
>>>> E.g. it could be a server side restriction but also a TLS protocol
>>>> issue.
>>>>
>>>> Check if basic authorization is really supported by the server (it's a
>>>> bit outdated due to security reasons).
>>>>
>>>> Then I would try
>>>>  --secure-protocol=TLSv1_2
>>>> to see if there is a difference.
>>>>
>>>> Next would be a tcpdump/wireshark session to see what is going on on the
>>>> protocol level.
>>>>
>>>> Regards, Tim
>>>>
>>>> On 30.10.19 22:19, address@hidden
>>>> <mailto:address@hidden> <mailto:address@hidden> wrote:
>>>>> Hello,
>>>>> I am not sure if my issue is a bug, but I have interesting problem
>>>>> below.
>>>>>
>>>>> We are posting xml file to server, if the file has under 10 kB then
>>>>> there is no problem, but if the file is bigger, there is "Retrying"
>>>>> problem. In the debug mode log says:
>>>>>
>>>>> [writing BODY file stockInfo.xml_trn_o1.xml ... Closed 4/SSL 0x022ed8d8
>>>>> Retrying.
>>>>>
>>>>> Wget command is:
>>>>>
>>>>> wget
>>>>> https://ws-dev.specialized.com/soa-infra/resources/GWS/StockInfo/Rest/api/v1
>>>>>  --http-user= xx --http-passwd= yy --post-file=stockInfo.xml_trn_o1.xml
>>>>> --header="Content-Type: application/xml" --header="Authorization: Basic
>>>>> xx" --header="Accept: application/xml" --header="X-Requested-With: x"
>>>>> --output-document=soapResponse.xml
>>>>>
>>>>> The Wget version is: GNU Wget 1.19.4 built on mingw32.
>>>>>
>>>>> But the problem is on actual version too.
>>>>>
>>>>> I have tried 3 different PCs with 3 different network providers.
>>>>>
>>>>> OSs:Windows Server 2008 R2 Standard SP1 64 bit, Windows 10 Pro 32 bit.
>>>>>
>>>>> Thank you in advance for any response.
>>>>>
>>>>> Kind Regards.
> 

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]