You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Bryan Pendleton <bp...@gmail.com> on 2016/01/30 23:03:44 UTC

Download mirror pages acting funny?

The Derby download pages, such as

	http://db.apache.org/derby/releases/release-10.11.1.1.html
and
	http://db.apache.org/derby/releases/release-10.12.1.1.html

are acting funny for me; they aren't picking a mirror download
site properly, and are showing:

	You are currently using [preferred].

Is this happening for anybody else?

thanks,

bryan

Re: Download mirror pages acting funny?

Posted by Rick Hillegas <ri...@gmail.com>.
On 2/1/16 7:56 PM, Bryan Pendleton wrote:
>>>     http://db.apache.org/derby/releases/
>>>
>>> shows both the html and the cgi, and it isn't obvious which to click 
>>> on.
>> Ha! I've never visited that page. Do we link to that page from 
>> somewhere on our website?
>
> No, I don't think we do.
>
> I think the reason I got there is that I had downloaded some other 
> release, e.g.,
>
>     http://db.apache.org/derby/releases/release-10.9.1.0.html
>
> which *is* linked to from derby_downloads.html.
>
> Then, I wanted a different release, and that page was in my browser
> history, and so my browser helpfully filled in that URL, and I
> decided just to back space over the stuff at the end and I was
> left with the problematic URL
>
>     http://db.apache.org/derby/releases/
>
> So it was a combination of me trying to 'guess' a URL, together with
> the fact that the valid download URLs for various releases are all
> extensions of that some common base URL.
>
> Plus, the index page that it showed me looked right; I just made the
> (incorrect) assumption that since the HTML extension was correct for
> release 10.9 and 10.10, it would in turn be the correct extension
> for 10.11 and 10.12 as well.
>
> I think I might not be the only person who would download
>
>     http://db.apache.org/derby/releases/release-10.9.1.0.html
> and
>     http://db.apache.org/derby/releases/release-10.10.1.1.html
>
> and then jump to the conclusion that you could just follow the
> progression from '9' to '10' to '11' to '12 and try to reference
>
>     http://db.apache.org/derby/releases/release-10.11.1.1.html
> and
>     http://db.apache.org/derby/releases/release-10.12.1.1.html
>
> Which is essentially what I did.
>
> I think we're just somewhat cursed by having such a long history
> of releases, and by the unfortunate fact that the URL naming
> convention changed in a fairly subtle way at release 10.11, and
> it was doubly-unfortunate that the new system leaves HTML files
> named according to the old convention which are NOT valid pages.
>
> If you're OK with the proposal to put the index.html in place, that
> will at least partly fix the problem, although it won't protect
> people who attempt to 'predict' the URL based on our naming
> convention, and thus stumble into URLs which look correct, but are
> in fact wrong.
Sounds good to me. Thanks!
>
> thanks,
>
> bryan
>
>


Re: Download mirror pages acting funny?

Posted by Bryan Pendleton <bp...@gmail.com>.
>>     http://db.apache.org/derby/releases/
>>
>> shows both the html and the cgi, and it isn't obvious which to click on.
> Ha! I've never visited that page. Do we link to that page from somewhere on our website?

No, I don't think we do.

I think the reason I got there is that I had downloaded some other release, e.g.,

	http://db.apache.org/derby/releases/release-10.9.1.0.html

which *is* linked to from derby_downloads.html.

Then, I wanted a different release, and that page was in my browser
history, and so my browser helpfully filled in that URL, and I
decided just to back space over the stuff at the end and I was
left with the problematic URL

	http://db.apache.org/derby/releases/

So it was a combination of me trying to 'guess' a URL, together with
the fact that the valid download URLs for various releases are all
extensions of that some common base URL.

Plus, the index page that it showed me looked right; I just made the
(incorrect) assumption that since the HTML extension was correct for
release 10.9 and 10.10, it would in turn be the correct extension
for 10.11 and 10.12 as well.

I think I might not be the only person who would download

	http://db.apache.org/derby/releases/release-10.9.1.0.html
and
	http://db.apache.org/derby/releases/release-10.10.1.1.html

and then jump to the conclusion that you could just follow the
progression from '9' to '10' to '11' to '12 and try to reference

	http://db.apache.org/derby/releases/release-10.11.1.1.html
and
	http://db.apache.org/derby/releases/release-10.12.1.1.html

Which is essentially what I did.

I think we're just somewhat cursed by having such a long history
of releases, and by the unfortunate fact that the URL naming
convention changed in a fairly subtle way at release 10.11, and
it was doubly-unfortunate that the new system leaves HTML files
named according to the old convention which are NOT valid pages.

If you're OK with the proposal to put the index.html in place, that
will at least partly fix the problem, although it won't protect
people who attempt to 'predict' the URL based on our naming
convention, and thus stumble into URLs which look correct, but are
in fact wrong.

thanks,

bryan


Re: Download mirror pages acting funny?

Posted by Rick Hillegas <ri...@gmail.com>.
On 1/31/16 6:30 PM, Bryan Pendleton wrote:
>> The mirrored (most current) releases always have two files governing 
>> them:
>>
>> 1) An html file which you DON'T click on.
>>
>> 2) A cgi file. That's what you DO click on.
>
> Thanks, Rick, this makes sense.
>
> And thanks very much for cleaning up the issues that Infra found and 
> logged.
>
> I think that I got myself confused because this page:
>
>     http://db.apache.org/derby/releases/
>
> shows both the html and the cgi, and it isn't obvious which to click on.
Ha! I've never visited that page. Do we link to that page from somewhere 
on our website? I always navigate to releases from 
http://db.apache.org/derby/derby_downloads.html.
>
> Infrastructure suggested that we put an "index.html" into this
> directory, which would list ONLY the files that we are supposed
> to click on, NOT the files that we DON'T click on.
>
> It seems to me that the (small) downside is that if we had an index.html
> in this directory, then each time we make a new release, we'd have to
> update our index.html.
>
> We'd put that in our release checklist.
>
> What do you think?
Either that or remove any website references to that directory. Any 
reason why we should support navigating to that directory directly 
rather than coming in through the official download page?

An extra step in the release process isn't a deal killer, particularly 
if we could find a way to automate this step. Over the last 10 years 
we've gradually paired down the number of manual interventions (aka 
places where the release manager could mess up).

Thanks,
-Rick
>
> thanks,
>
> bryan
>
>
>


Re: Download mirror pages acting funny?

Posted by Bryan Pendleton <bp...@gmail.com>.
> The mirrored (most current) releases always have two files governing them:
>
> 1) An html file which you DON'T click on.
>
> 2) A cgi file. That's what you DO click on.

Thanks, Rick, this makes sense.

And thanks very much for cleaning up the issues that Infra found and logged.

I think that I got myself confused because this page:

	http://db.apache.org/derby/releases/

shows both the html and the cgi, and it isn't obvious which to click on.

Infrastructure suggested that we put an "index.html" into this
directory, which would list ONLY the files that we are supposed
to click on, NOT the files that we DON'T click on.

It seems to me that the (small) downside is that if we had an index.html
in this directory, then each time we make a new release, we'd have to
update our index.html.

We'd put that in our release checklist.

What do you think?

thanks,

bryan



Re: Download mirror pages acting funny?

Posted by Rick Hillegas <ri...@gmail.com>.
On 1/31/16 3:30 PM, Bryan Pendleton wrote:
> On 1/30/2016 2:03 PM, Bryan Pendleton wrote:
>> The Derby download pages, such as
>>
>>      http://db.apache.org/derby/releases/release-10.11.1.1.html
>> and
>>      http://db.apache.org/derby/releases/release-10.12.1.1.html
>>
>> are acting funny for me; they aren't picking a mirror download
>> site properly, and are showing:
>>
>>      You are currently using [preferred].
>
> It looks like part of the problem is that there are two sets of
> download pages for the 10.11 and 10.12 releases:
>
>      http://db.apache.org/derby/releases/release-10.11.1.1.html
>      http://db.apache.org/derby/releases/release-10.12.1.1.html
> and
>      http://db.apache.org/derby/releases/release-10.11.1.1.cgi
>      http://db.apache.org/derby/releases/release-10.12.1.1.cgi
>
> The ".cgi" pages are generating valid download links; the ".html"
> pages are not.
>
> I got to these ".html" pages for the recent releases by looking at
>
>      http://db.apache.org/derby/releases/
>
> It looks like we have some cleanup work to do on our release
> distribution pages on the site; the Apache Infrastructure team have
> filed a couple of other issues that they noticed while trying to
> help me resolve this problem.
>
> Rick, do you know your way around this infrastructure well enough
> to help me with these tasks?
>
> thanks,
>
> bryan
>
>
>
>
Hi Bryan,

The mirrored (most current) releases always have two files governing them:

1) An html file which you DON'T click on. The html file contains that 
weird [preferred] verbiage which is part of the magic which actually 
indirects you to the mirroring sites.

2) A cgi file. That's what you DO click on. The cgi file and the html 
file cooperate with one another in order to effect the mirroring. I 
don't understand this stuff. It just works.

When a release is transferred from the mirrors to the archives, then the 
release manager has to remove the cgi file and update the html file, 
removing the [preferred] verbiage and replacing it with hardcoded links 
to the archive locations.

The mirroring looks to me as though it's working correctly right now.

Modulo my ignorance about cgi, does that help?

Thanks,
-Rick

Re: Download mirror pages acting funny?

Posted by Bryan Pendleton <bp...@gmail.com>.
On 1/30/2016 2:03 PM, Bryan Pendleton wrote:
> The Derby download pages, such as
>
>      http://db.apache.org/derby/releases/release-10.11.1.1.html
> and
>      http://db.apache.org/derby/releases/release-10.12.1.1.html
>
> are acting funny for me; they aren't picking a mirror download
> site properly, and are showing:
>
>      You are currently using [preferred].

It looks like part of the problem is that there are two sets of
download pages for the 10.11 and 10.12 releases:

      http://db.apache.org/derby/releases/release-10.11.1.1.html
      http://db.apache.org/derby/releases/release-10.12.1.1.html
and
      http://db.apache.org/derby/releases/release-10.11.1.1.cgi
      http://db.apache.org/derby/releases/release-10.12.1.1.cgi

The ".cgi" pages are generating valid download links; the ".html"
pages are not.

I got to these ".html" pages for the recent releases by looking at

      http://db.apache.org/derby/releases/

It looks like we have some cleanup work to do on our release
distribution pages on the site; the Apache Infrastructure team have
filed a couple of other issues that they noticed while trying to
help me resolve this problem.

Rick, do you know your way around this infrastructure well enough
to help me with these tasks?

thanks,

bryan




Re: Download mirror pages acting funny?

Posted by Bryan Pendleton <bp...@gmail.com>.
On 1/30/2016 7:27 PM, Fang Yun wrote:
>   the download link in page is like as below:
>
> http://db.apache.org/derby/releases/*[preferred]/*db/derby/db-derby-10.11.1.1/db-derby-10.11.1.1-bin.zip
>
> which is wrong. Maybe the construction of this page has something wrong.
>

Thanks for confirming that you see the same thing, Yun.

I have followed up with the Infrastructure team to see if they
can help me figure out what got broken.

bryan


Re: Download mirror pages acting funny?

Posted by Fang Yun <fa...@gmail.com>.
Yes, I click the both links,  the download link in page is like as below:

http://db.apache.org/derby/releases/*[preferred]/*
db/derby/db-derby-10.11.1.1/db-derby-10.11.1.1-bin.zip

which is wrong. Maybe the construction of this page has something wrong.

Best regards,
Yun

On Sun, Jan 31, 2016 at 6:03 AM, Bryan Pendleton <bpendleton.derby@gmail.com
> wrote:

> The Derby download pages, such as
>
>         http://db.apache.org/derby/releases/release-10.11.1.1.html
> and
>         http://db.apache.org/derby/releases/release-10.12.1.1.html
>
> are acting funny for me; they aren't picking a mirror download
> site properly, and are showing:
>
>         You are currently using [preferred].
>
> Is this happening for anybody else?
>
> thanks,
>
> bryan
>