Re: [Savannah-hackers-public] Redirect gnutelephony.org
O'siyo Therese, do I need to anything further on my end with dns? Th?r?se Godefroy wrote: > Hello Bob, > > It seems that this project fell through the cracks. ;) > > Le 07/02/2018 19:18, Bob Proulx a écrit : > >>> Perhaps we should put in a redirect in that case so that if someone > >>> arrives at Savannah by an unexpected and undesired name that they get > >>> redirected to the main domain. > > > > I have done this. > > Thanks! > > [...] > > I have no idea how localization is done. That is done with a cookie? > > I immediately have twenty questions but will hold them off for now. > > Someone else was asking about localization and I had no idea how it > > worked. > > It uses Apache MultiViews + plenty of rewrite rules + "Set language" at > the top of the page to choose a different language for the session. For > instance your browser's preferred language is French, but you want to > read the English pages because the French translations are lousy (this > never happens in real life, of course :)). Ineiev could explain how it > works. I can't. > [...] > > 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 think you mean this address: > >>> > >>> https://www.gnu.org/software/gnucomm/ > > Yes, of course. You can also use > https://www.gnu.org/software/gnucomm/gnucomm.html > > [...] > >> See the whole story below. > > > > I want to send out notice of the above and not hold it while I read > > and understand the rest of what you have written. So I will send this > > now and then queue up the below for further reading a little later in > > the day when I have time. At the moment other urgencies are dragging > > my attention away. > > Thanks in advance for setting up this redirection (or rewrite rule). > > Best regards, > Thérèse
Re: [Savannah-hackers-public] Redirect gnutelephony.org
Hello David, Le 03/03/2018 17:41, Chief Sugar a écrit : > O'siyo Therese, > > do I need to anything further on my end with dns? Both www.gnutelephony.org and wiki.gnutelephony.org reach savannah now, so it's OK. I don't know whether any other subdomains would be worth redirecting to Savannah. Maybe download.gnutelephony.org? I have seen a couple of links to it. All the best, Thérèse
Re: [Savannah-hackers-public] Redirect gnutelephony.org
Hello Bob, It seems that this project fell through the cracks. ;) Le 07/02/2018 19:18, Bob Proulx a écrit : >>> Perhaps we should put in a redirect in that case so that if someone >>> arrives at Savannah by an unexpected and undesired name that they get >>> redirected to the main domain. > > I have done this. Thanks! [...] > I have no idea how localization is done. That is done with a cookie? > I immediately have twenty questions but will hold them off for now. > Someone else was asking about localization and I had no idea how it > worked. It uses Apache MultiViews + plenty of rewrite rules + "Set language" at the top of the page to choose a different language for the session. For instance your browser's preferred language is French, but you want to read the English pages because the French translations are lousy (this never happens in real life, of course :)). Ineiev could explain how it works. I can't. [...] 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 think you mean this address: >>> >>> https://www.gnu.org/software/gnucomm/ Yes, of course. You can also use https://www.gnu.org/software/gnucomm/gnucomm.html [...] >> See the whole story below. > > I want to send out notice of the above and not hold it while I read > and understand the rest of what you have written. So I will send this > now and then queue up the below for further reading a little later in > the day when I have time. At the moment other urgencies are dragging > my attention away. Thanks in advance for setting up this redirection (or rewrite rule). Best regards, Thérèse
Re: [Savannah-hackers-public] Redirect gnutelephony.org
Hello Thérèse,
> > Perhaps we should put in a redirect in that case so that if someone
> > arrives at Savannah by an unexpected and undesired name that they get
> > redirected to the main domain.
I have done this. The redirect for other domains is now in place. It
shouldn't cause any change at all for the standard domains. For DNS
domains that point to the same IP address as Savannah those will see
an http redirect which will change the URL in their browser to show a
canonical name. The causes them to be in the same security domain and
therefore session cookies and everything will work normally.
This only works well for http. Since https requires a valid
certificate it can't work well with https. But I did set up an https
redirect as well. It will, as it must be, an invalid certificate.
But it seemed better to provide this for clients that don't check
validity than to have them arrive and stay at the wrong domain.
I also added a test to the savannah-tests testsuite to test that this
redirect is in place.
Thérèse Godefroy wrote:
> Bob Proulx wrote:
> > And because of the domain difference it will use a cookie for
> > the other domain instead of the Savannah one.
>
> Will this happen if the URL is not redirected, but rewritten (as
> suggested in my last message)?
That is a separate issue because that needs to know about the listed
other domains. Doing the http redirect for unknown domains just needs
to know that it isn't savannah.{non,}gnu.org. That's simple and
generic. But doing it for other domains requires a configuration for
each domain. And a test for each one too.
I am pretty sure the RewriteRule suggested needed flags [R,L] added to
make it do what you wanted it to do. However in the case suggested
simply using a Redirect is simpler and more direct. I will say
something in detail in reply to that message in a moment.
> I assume the cookie will be for the
> rewritten version (gnu.org/software/gnucomm/), not the original domain
> (gnutelephony.org).
Yes. After a redirect the browser then applies all rules associated
with the new domain.
> In fact, the only cookie I ever saw on gnu.org is the language cookie
> which goes with the "set language" feature.
I have no idea how localization is done. That is done with a cookie?
I immediately have twenty questions but will hold them off for now.
Someone else was asking about localization and I had no idea how it
worked.
> > Perhaps we should put in a redirect in that case so that if someone
> > arrives at Savannah by an unexpected and undesired name that they get
> > redirected to the main domain.
>
> Isn't it what the default vhost does already?
No. That wasn't the way it worked before. Before a default vhost
simply served the request. That left the URL in the browser location
bar to be any of an infinite number of possible names, each creating a
new browser security domain and an indepedent set of cookies. But as
of today that is the way it is working now moving forward. Now if
someone arrives by using a different name a redirect will take them
back to a canonical name.
> What really happens is
> that if someone arrives at www.gnu.org by an unexpected name, they get
> redirected to the Savannah home page. And if they arrive directly at
> Savannah, they stay there.
The historical setup of everything is such a maze of twisty little
passages all different. I didn't know that www.gnu.org had such a
redirect in place. To my sensibilities that seems odd. But I will
just accept it and keep going because, "C'est la vie".
In any case I think we have finally caught up the Savannah half of
this configuration, now in 2018, after it has probably been like this
for 15 years. Oh well.
This is only half of this problem. The browser domain context half.
> > That would clean up this current
> > situation. I think that would make the best of the situation since we
> > can't prevent the world from pointing to it.
> >
> > I will make that change sometime this week when I get enough time to
> > make the change and test it.
>
> Thanks!
That part is done. If you visit http://gnutelephony.org/ now you will
see the difference in the browser location bar. And the behavior
should then follow correctly. That is the only difference you should
notice. Other appearances should be the same since it is rendering
the same page.
> >> 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 think you mean this address:
> >
> > https://www.gnu.org/software/gnucomm/
>
> Either one will do. gnucomm/index.html is "symlinked" (not exactly,
> because this is done by mod_rewrite) to gnucomm/gnucomm.html.
When I visit http://www.gnu.org/gnucomm/gnucomm.html I get a 404 Not Found.
wget -O/dev/null -S -q http://www.gnu.org/gnucomm/gnucomm.html
HTTP/1.1 404 Not Found
Date: Wed, 07 Feb 2018 18:14:19 GMT
Re: [Savannah-hackers-public] Redirect gnutelephony.org
Hello Bob, Thanks for trying to solve this issue. Le 05/02/2018 06:52, Bob Proulx a écrit : > 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), > > That seems like a very confusing configuration. Because then a user > would find themselves on what looks like Savannah but by a different > domain. This is already happening. It's still better than ending up on whatevername.org, as they did before. At least on the Savannah home page they have a search box, and if they type "telephony" they get 2 relevant projects: Bayonne and Gnucomm. > And because of the domain difference it will use a cookie for > the other domain instead of the Savannah one. Will this happen if the URL is not redirected, but rewritten (as suggested in my last message)? I assume the cookie will be for the rewritten version (gnu.org/software/gnucomm/), not the original domain (gnutelephony.org). In fact, the only cookie I ever saw on gnu.org is the language cookie which goes with the "set language" feature. > Perhaps we should put in a redirect in that case so that if someone > arrives at Savannah by an unexpected and undesired name that they get > redirected to the main domain. Isn't it what the default vhost does already? What really happens is that if someone arrives at www.gnu.org by an unexpected name, they get redirected to the Savannah home page. And if they arrive directly at Savannah, they stay there. > That would clean up this current > situation. I think that would make the best of the situation since we > can't prevent the world from pointing to it. > > I will make that change sometime this week when I get enough time to > make the change and test it. Thanks! >> 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 think you mean this address: > > https://www.gnu.org/software/gnucomm/ Either one will do. gnucomm/index.html is "symlinked" (not exactly, because this is done by mod_rewrite) to gnucomm/gnucomm.html. [...] > But I would want to be convinced. Please say a few words in favor of > why this feature needs to be created for the first time for this > project? And if so and if it is a desirable enough feature then I > could see that we would want to make that possibility available to all > other GNU projects as well. See the whole story below. > Note that it will require a test for this feature to be added to the > test project as well. If a test is not added then there is no > guarentee that it will not be broken at some time in the future > because it isn't otherwise documented. After a few years (months?) > everyone will have forgotten about the configuration A vhost is rather easy to detect. You can add explanations in the configuration file. > and then it would > be lost and broken. I am trying to think of a good way to have a list > of available redirects available for download such that the entire set > could be automatically tested. Because trying to keep the test > framework updated would otherwise be problematic. They would probably > always lag behind and be out of date. > > It also looks like email address @gnutelephony.org for the registered > user dyfet must be broken because the mail would attempt to connect to > Savannah which does not receive email. That needs to be updated. This address has been broken for 2 1/2 years. This is just one more broken email address. Every time I try an address that I find around gnu.org, I cross fingers, but very often it doesn't work. > Bob gnutelephony.org covers 7 GNU projects (bayonne, sipwitch commoncpp, ccscript, ccaudio, ccrtp, and the GNU telephony subsystem, gnucomm). They are all maintained by David Sugar. gnutelephony.org is more or less equivalent to gnucomm, but with a wider scope. It became independent in 2005, and accumulated a lot of data until the server went down in 2015. By then, there were plenty of links to it all over the web. As a quick fix, David made gnutelephony.org point to another (unrelated) site that he is involved with. But this made it look like gnutelephony.org had been hijacked. Last October, I tried to fix a few dead links which were reported by linc, and found a big mess in the telephony pages. I also found the Wayback Machine archive of gnutelephony.org. After discussing with David, I imported as much data as possible to the relevant pages. Now gnucomm is more or less equivalent to the gnutelephony main page. It acts as an general index for the other telephony projects. The next step was to point gnutelephony.org to one of the FSF servers and redirect to https://www.gnu.org/software/gnucomm/ (strictly equivalent to https://www.gnu.org/software/gnucomm/gnucomm.html). We contacted sysad...@fsf.org, and Ian said it was OK to use 208.118.235.148 (wildebeest). He also said he would set up
Re: [Savannah-hackers-public] Redirect gnutelephony.org
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), That seems like a very confusing configuration. Because then a user would find themselves on what looks like Savannah but by a different domain. And because of the domain difference it will use a cookie for the other domain instead of the Savannah one. Perhaps we should put in a redirect in that case so that if someone arrives at Savannah by an unexpected and undesired name that they get redirected to the main domain. That would clean up this current situation. I think that would make the best of the situation since we can't prevent the world from pointing to it. I will make that change sometime this week when I get enough time to make the change and test it. > 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 think you mean this address: https://www.gnu.org/software/gnucomm/ As far as I can see it would be the first project to have such a redirect set up on Savannah. Therefore I am immediately suspicious of the new feature. I think it could become an unmanageable mess if many projects were all needing to be configured with redirects from Savannah. Therefore on the basis of cofiguration mess I would rather not see this added. Simple is best and this is a creeping feature. But it does appear to be an official GNU project. It is technically possible. So I won't block this from happening. And many things about the GNU project require that someone manually edit files. So this wouldn't be that much different in spirit. But I would want to be convinced. Please say a few words in favor of why this feature needs to be created for the first time for this project? And if so and if it is a desirable enough feature then I could see that we would want to make that possibility available to all other GNU projects as well. Note that it will require a test for this feature to be added to the test project as well. If a test is not added then there is no guarentee that it will not be broken at some time in the future because it isn't otherwise documented. After a few years (months?) everyone will have forgotten about the configuration and then it would be lost and broken. I am trying to think of a good way to have a list of available redirects available for download such that the entire set could be automatically tested. Because trying to keep the test framework updated would otherwise be problematic. They would probably always lag behind and be out of date. It also looks like email address @gnutelephony.org for the registered user dyfet must be broken because the mail would attempt to connect to Savannah which does not receive email. That needs to be updated. Bob
Re: [Savannah-hackers-public] Redirect gnutelephony.org
-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: > > ServerName gnutelephony.org ServerAlias > www.gnutelephony.org Redirect / > http://www.gnu.org/software/gnucomm/gnucomm.html > > (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: ServerName gnutelephony.org ServerAlias www.gnutelephony.org ServerAlias wiki.gnutelephony.org RewriteEngine on RewriteRule ^(.*)$ http://www.gnu.org/software/gnucomm/gnucomm.html 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-
Re: [Savannah-hackers-public] Redirect gnutelephony.org
> > 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: ServerName gnutelephony.org ServerAlias www.gnutelephony.org Redirect / http://www.gnu.org/software/gnucomm/gnucomm.html (and then apachectl restart). I'm not sure how to deal with HTTPS: Savannah has no certificates for gnutelephony.org. signature.asc Description: Digital signature
Re: [Savannah-hackers-public] Redirect gnutelephony.org
Hello, Thérèse; 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 whois gnutelephony.org says, Domain Name: GNUTELEPHONY.ORG ... Admin Name: David Sugar Isn't it David who controls gnutelephony.org? signature.asc Description: Digital signature
Re: [Savannah-hackers-public] Redirect gnutelephony.org
Le 19/01/2018 13:39, Thérèse Godefroy a écrit : > Hello, > > 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 Correction: http(s)://www.gnu.org/software/gnucomm/gnucomm.html > Could you help us with this? Thanks in advance. > > Best regards, > Thérèse > >
