On 24 November 2010 11:43, Niklas Gustavsson <nik...@protocol7.com> wrote: > On Wed, Nov 24, 2010 at 12:31 PM, sebb <seb...@gmail.com> wrote: >> I just discovered that I was accidentally using >> >> http://hudson.zones.apache.org/ >> instead of >> https://hudson.apache.org/ >> to download some JMeter build files. > > Sounds weird, you should be getting a simple HTTP redirect to > https://hudson.apache.org/ after which the download should work the > exakt same way. E.g.: > $ curl -v > http://hudson.zones.apache.org/hudson/job/Abdera-trunk/ws/trunk/pom.xml > * About to connect() to hudson.zones.apache.org port 80 (#0) > * Trying 140.211.11.8... connected > * Connected to hudson.zones.apache.org (140.211.11.8) port 80 (#0) >> GET /hudson/job/Abdera-trunk/ws/trunk/pom.xml HTTP/1.1 >> User-Agent: curl/7.19.7 (i386-apple-darwin10.2.0) libcurl/7.19.7 zlib/1.2.3 >> Host: hudson.zones.apache.org >> Accept: */* >> > < HTTP/1.1 302 Found > < Date: Wed, 24 Nov 2010 11:41:26 GMT > < Server: Apache/2.2.14 (Ubuntu) > < Location: https://hudson.apache.org/hudson/job/Abdera-trunk/ws/trunk/pom.xml
Actually, the URL was different elsewhere as well: [1] http://hudson.zones.apache.org/hudson/job/JMeter-trunk/ws/trunk/dist/ as against [2] https://hudson.apache.org/hudson/job/JMeter-trunk/lastSuccessfulBuild/artifact/trunk/dist/ [1] converts to https://hudson.apache.org/hudson/job/JMeter-trunk/ws/trunk/dist/ which is about 10x slower than [2]. Perhaps that gives a clue as to the problem? > >> Is it possible that the wrong URL is being used in Hudson somewhere? > > Hudson slaves communicate over SSH and there isn't really URLs > involved as far as I know. > >> I'm sure the http: URL used to work OK, but I'm not sure how long ago >> that was - possibly a month or more. > > The old domain (and http -> https) was redirected when the new Hudson > master was set up. > > /niklas >
