On May 17, 2010, at 18:13 , Clement Escoffier wrote: > On 17.05.2010, at 18:01, Matt Tennant wrote: > >> Ah, very interesting. Thanks. I didn't even notice the difference >> between the html and cgi pages, since I've seen the cgi one many times and >> they basically look identical. Anyway, the junit4osgi pages link to the >> downloads.html page, which is how I happened to get there this time, maybe >> those links should be updated: >> >> http://felix.apache.org/site/apache-felix-ipojo-junit4osgi-tutorial.html > > I've just updated the page. It will be updated during the next > synchronization. > The only tricky thing ... the link was generated by a regular confluence link > : [downloads|downloads].
This needs an explanation. The page in Confluence (in other words the html page) is used as a template by the CGI script. The CGI script actually fetches the list of available mirrors, does some magic to determine the one closest to you, and subsequently allows you to select different mirrors and download files from your selected mirror. This functionality was not available from Confluence, which is why the CGI is there in the first place. In other words, if you link to downloads, do not use a regular Confluence link, but use the CGI page instead (you probably need to hardcode that). Greetings, Marcel --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
