On Fri, May 16, 2014 at 12:05 PM, Christopher Faylor wrote:
> There will probably be some gotchas to work out for places which refer to
> http://cygwin.com/ directly. Please send any issues here, as always.
It appears it is not forcing HTTPS through a 301 redirect, is this intentional?
$ wget --spider cygwin.com
Spider mode enabled. Check if remote file exists.
--2014-05-16 17:04:43-- http://cygwin.com/
Resolving cygwin.com (cygwin.com)... 209.132.180.131
Connecting to cygwin.com (cygwin.com)|209.132.180.131|:80... connected.
HTTP request sent, awaiting response... 200 OK
Example of the 301
$ wget --spider github.com
Spider mode enabled. Check if remote file exists.
--2014-05-16 17:04:36-- http://github.com/
Resolving github.com (github.com)... 192.30.252.130
Connecting to github.com (github.com)|192.30.252.130|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/ [following]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
