Re: Updated: setup (2.880)
- Date: Tue, 27 Jun 2017 19:25:10 -0400
- From: Lee <ler762@xxxxxxxxx>
- Subject: Re: Updated: setup (2.880)
On 6/27/17, Nellis, Kenneth wrote:
> From: Csaba Raduly
>> I also couldn't reproduce your scenario.
>> Since it's reproducible for you, you could (if you're curious) run
>> wget with the -d (--debug) switch or break out the heavy artillery:
>> install Wireshark and look at the HTTP headers sent and received by
> Thanx, Csaba, for your interest. Another test with -d is easy enough,
> so here it is:
> $ wget -d -O setup-x86_64.exe http://cygwin.com/setup-x86_64.exe
> Setting --output-document (outputdocument) to setup-x86_64.exe
> DEBUG output created by Wget 1.19.1 on cygwin.
> Reading HSTS entries from /home/knellis/.wget-hsts
> --2017-06-27 16:42:01-- http://cygwin.com/setup-x86_64.exe
> Resolving cygwin.com... 22.214.171.124
> Caching cygwin.com => 126.96.36.199
> Connecting to cygwin.com|188.8.131.52|:80... connected.
> Created socket 5.
> Releasing 0x0000000600066420 (new refcount 1).
> ---request begin---
> GET /setup-x86_64.exe HTTP/1.1
> User-Agent: Wget/1.19.1 (cygwin)
> Accept: */*
> Accept-Encoding: identity
> Host: cygwin.com
> Connection: Keep-Alive
> ---request end---
> HTTP request sent, awaiting response...
> ---response begin---
> HTTP/1.1 200 OK
> Server: Apache
> ETag: "16b1f9e-dd613-55161a558184f"
> Accept-Ranges: bytes
> Cache-Control: max-age=0
> Expires: Tue, 27 Jun 2017 20:40:06 GMT
> Vary: Accept-Encoding
> Content-Encoding: gzip
> Content-Security-Policy: default-src 'self' http: https:
> Keep-Alive: timeout=30, max=20
> Content-Length: 877562
> Content-Type: application/octet-stream
> Last-Modified: Wed, 07 Jun 2017 16:58:31 GMT
> Date: Tue, 27 Jun 2017 20:39:27 GMT
> Age: 0
> Via: 1.1 ironport.tms.local:80 (Cisco-WSA/10.1.0-204)
it looks like you've got a cisco ironport playing mitm with your traffic.
<.. snip ..>
> Note the response from the Apache server:
>> Content-Encoding: gzip
nobody else gets that, and you don't if you do a wget from home -
correct? So it's most probably coming from the ironport & not the
cygwin web server
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple