Dear,
Is it a problem if we redirect all http requests to https ?
/root@sflow:~# wget -O -
https://mirror.nbtelecom.com.br/debian/project/trace/mirror.nbtelecom.com.br
-q//
//Tue Oct 15 13:03:12 UTC 2019//
//Date: Tue, 15 Oct 2019 13:03:12 +0000//
//Date-Started: Tue, 15 Oct 2019 13:00:02 +0000//
//Archive serial: 2019101502//
//Used ftpsync version: 20171018//
//Creator: ftpsync 20171018//
//Running on host: sf.nbtelecom.com.br//
//Architectures: all amd64 arm64 armel armhf i386 mips mips64el mipsel
powerpc ppc64el s390x source//
//Architectures-Configuration: ALL//
//Upstream-mirror: sft.if.usp.br//
//Rsync-Transport: undefined//
//Total bytes received in rsync: 215350//
//Total time spent in stage1 rsync: 111//
//Total time spent in stage2 rsync: 79//
//Total time spent in rsync: 190//
//Average rate: 1133 B/s/
Best Regards,
Pedro Alves
Em 15/10/2019 03:40, Peter Palfrader escreveu:
I have removed your mirror again, as it's broken now.
| weasel@orinoco:~$ wget -O -
http://mirror.nbtelecom.com.br/debian/project/trace/mirror.nbtelecom.com.br -q
| <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
| <html><head>
| <title>400 Bad Request</title>
| </head><body>
| <h1>Bad Request</h1>
| <p>Your browser sent a request that this server could not understand.<br />
| Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
| Instead use the HTTPS scheme to access this URL, please.<br />
| <blockquote>Hint: <a
href="https://nbtelecom.dl.sourceforge.net/";><b>https://nbtelecom.dl.sourceforge.net/</b></a></blockquote></p>
Please re-submit your mirror should it come back.
On Thu, 26 Sep 2019, Pedro Alves wrote:
Trace Url:
http://mirror.nbtelecom.com.br/debian/project/trace/mirror.nbtelecom.com.br
