savannah-hackers-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers-public] Redirect gnutelephony.org


From: Thérèse Godefroy
Subject: Re: [Savannah-hackers-public] Redirect gnutelephony.org
Date: Sun, 4 Feb 2018 16:01:18 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Ineiev, hello everybody,

Le 20/01/2018 13:46, Ineiev a écrit :
>>> On Fri, Jan 19, 2018 at 01:41:51PM +0100, Thérèse Godefroy
>>> wrote:
>>>>> The old gnutelephony.org website, which went down in August
>>>>> 2015, now points to savannah.nongnu.org (208.218.235.79),
>>>>> and most of it has been imported to the various projects
>>>>> that David Sugar maintains (bayonne, ccaudio, ccrtp,
>>>>> ccscript, commoncpp, gnucomm, and sipwitch). The gnucomm 
>>>>> home page acts as a general index for the other 6.
>>>>> 
>>>>> What we would like to do now is redirect all requests for 
>>>>> http(s)://gnutelephony.org/* or
>>>>> http(s)://www.gnutelephony.org/* to 
>>>>> http(s)://www.gnu.org/gnucomm/gnucomm.html
> 
> I guess we should add something like this to 
> frontend0.gnu.org:/etc/apache2/sites-available/vhosts-gnu.org:
> 
> <VirtualHost *:80> ServerName gnutelephony.org ServerAlias
> www.gnutelephony.org Redirect /
> http://www.gnu.org/software/gnucomm/gnucomm.html </VirtualHost>
> 
> (and then apachectl restart).
> 
> I'm not sure how to deal with HTTPS: Savannah has no certificates 
> for gnutelephony.org.

It may be even better to do something like this:

<VirtualHost gnutelephony.org:80>
    ServerName gnutelephony.org
    ServerAlias www.gnutelephony.org
    ServerAlias wiki.gnutelephony.org
    RewriteEngine on
    RewriteRule ^(.*)$ http://www.gnu.org/software/gnucomm/gnucomm.html
</VirtualHost>

By the way, frontent0 is at 208.118.235.79, of course. This is what
the A record of gnutelephony.org points to now. www.gnutelephony.org
and wiki.gnutelephony.org are also listed.

I don't think HTTPS is very important in this case.

Many thanks.

Have a nice week,
David and Thérèse
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJadyA+AAoJEN8zjwg4B5HvvlIH/iDSKwS/Qp+K9JgWUHkJJYft
U7wy52K+B0eFb0LVFK9uEEogbzBz7ARTYCWHqUjm+rQuQdOUnZY4Zwximw6izdk3
NBBICoqIqY3asdXuby4W/qpTG6JEyqGmtZ8mxAnMTDKZtuBA9zRJVmemKN1+gsY3
JXKiK/kpIqvb92pDoWD6YLRs5CchvwJwW7K9bFZJgFZvpULbut2yfchV238NSmjA
A3IIiUt+SAy4quNEvrF6X2yvkFzkGZscJjH8TaBcwOqPNd+sCIWMbGcSdV/j3lKz
4W8100b9/uYia9kZdVTLhYZWlgQSofRqwIiJMsR9SzTujlRvG/7poa260abr5pU=
=A0Ol
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]