On 22 April 2018 at 12:12, Henk P. Penning <[email protected]> wrote: > On Sun, 22 Apr 2018, Jan Iversen wrote: > >> Date: Sun, 22 Apr 2018 12:42:39 +0200 >> From: Jan Iversen <[email protected]> >> To: [email protected] >> Subject: Re: svn commit: r1829770 - in /attic/site-json: build.props >> build.sh >> build.xml docs/projects/ lib/ xdocs/ > > >>> attic/site-json/docs/projects/ >> >> I think this is wrong ? The idea was to have projects/.htaccess with >> the rewrite to attic.js > > > Eh ; just a reminder ; the httpd config for www.a.o uses : > > RewriteCond "%%{}{REQUEST_URI}" "^/dist/([-a-zA-Z0-9]+)" > RewriteCond "/var/www/attic.apache.org/projects/%1.html" -f > RewriteRule ".*" "http://attic.apache.org/projects/%1.html"; [R=307,L] > > In other words : the /dist/GHOST/ redirects are triggered > by the presence of "attic.apache.org/projects/GHOST.html". > > The point is that the lookup [-f] has to fast. > In the future we should create a directory (like "flagged/") ; > possibly combine the two, as in : > > attic.a.o/retired/ > attic.a.o/retired/GHOST/ # retired flag > attic.a.o/retired/GHOST/add-banner # banner flag
The dist redirect needs the plain host name, e.g. ace, whereas AFAIK the banner processing needs FQDN, e.g. ace[.eu|us].apache.org. So that won't work unless the banner processing can be changed to use the plain host name. But I agree it would be good to reduce the number of files that have to be created/amended for a new retirement. > Does it make sense to have an (optional) 'dist' attribute, > for sites where "lowercase(name)" is not equal to the > the NAME in /dist/NAME ? Which 'name' are you referring to here? >> Jan I > > > HPP > > ------------------------------------------------------------ _ > Henk P. Penning, ICT-beta R Uithof MG-403 _/ \_ > Faculty of Science, Utrecht University T +31 30 253 4106 / \_/ \ > Leuvenlaan 4, 3584CE Utrecht, NL F +31 30 253 4553 \_/ \_/ > http://www.staff.science.uu.nl/~penni101/ M [email protected] \_/
