View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005598 | GNUnet | other | public | 2019-02-22 11:39 | 2019-05-12 13:29 |
Reporter | nikita | Assigned To | Christian Grothoff | ||
Priority | normal | Severity | text | Reproducibility | have not tried |
Status | closed | Resolution | not fixable | ||
Product Version | Git master | ||||
Target Version | 0.11.4 | Fixed in Version | 0.11.4 | ||
Summary | 0005598: Various files still point to old gnunet.org | ||||
Description | Most of our READMEs, excluding gnunet I think I fixed this, are still pointing to variations of gnunet.org while it should be old.gnunet.org in cases where it makes sense. It would be easier to have an appache config which tries old.gnunet.org for any given URL when gnunet.org fails for an URL before falling back to 404. | ||||
Tags | No tags attached. | ||||
|
This is major, because gnunet-gtk should be released around the same time and still has it. |
|
gnunet: URLs in comments remain gnunet-gtk: fixed Both should be updated to docs.gnunet.org, but this will take more time. |
|
Fast fix (ie don't do this): simply use old.gnunet.org in place. Proper fix: Link to the section on docs.gnunet.org and similar places. Annoying work, low hanging fruit for 0.11.1 |
|
When I write "files" I mean, clone the repos and run a recursive text search for "gnunet.org" in there. For gnunet this is now mostly src/ |
|
This is also upsetting web search results greatly and frustrates users that are hit with 404 on arrival. |
|
I like this approach and don't think we should intentionally break old pages https://4042302.org/ |
|
Let me stress the importance of the broken links: 1) it's bad publicity, people expect to find information even if in the end it turns out to be the old one 2) I get this question very often "where did XY go on the gnunet.org page? It's gone!" or something like that 3) Also wldhx gets this question. |
|
Since only grothoff can resolve this on the server side, assigned to grothoff |
|
Eh, I'm just not sure _how_ this can be done, especially given that there are like 3000+ URLs on old.gnunet.org and manually putting each of those into the configuration file with a redirection to old would seem, eh, excessive. I've not yet been able to find a general rule for "test if it exists locally, and if not redirect to old *if* it exists there". |
|
Note that we need this for now for Apache, in the future for nginx. |
|
server { # … location / { error_page 404 =302 https://old.gnunet.org$request_uri; try_files $uri $uri/ =404; } } For nginx, if I understand this https://4042302.org/how/ proposal right The idea is that upon 404, we try 302 and if that doesn't work, 404. Unless I'm wrong about how it's to be read. |
|
That's nginx syntax, gnunet.org runs Apache. I've tried this: RewriteCond %{REQUEST_URI} !-F RewriteCond https://old.gnunet.org%{REQUEST_URI} -U RewriteRule ^/(.*)$ https://old.gnunet.org/$1 [R=302,L] but with neither -F nor -U it works properly: the first condition always fails with -F (redirecting everything, including / and /en/) and always succeeds with -U (redirecting nothing). So neither test works properly for 404 status codes. |
|
Now, a possible solution: get nginx running on firefly, deploy the new Web site there, target DNS record for gnunet.org to firefly and then use the nginx rule to redirect to old.gnunet.org on tripwire. Now, except for the DNS change, that's something you have the rights to do... |
|
Okay. I still haven't gotten to reading the mail wrt firefly, I want to finish refactoring first (this week) and have some other things going on. |
|
It's a bit more difficult. Since some URLs, for example in your "GNU Name System: 2019 Edition" slides point to the old Drupal books, we need to make a Drupal Book -> Texinfo html pages redirect as well. Ideally this would happen in my rewrite of the bibliography: We link to the detail page of a single entry of the bibliography, identified by a unique URL. In addition to the current view and generated bibtex it contains further metadata like link to code and link to contemporary documentation (bib.gnunet.org/entry/gns/detail/documentation jumps to https://docs.gnunet.org/#First-steps-_002d-Using-the-GNU-Name-System or whatever we decide on.. just as a quick idea of the top of my head) |
|
so now that old.gnunet.org is mostly digital dust, I think the scope of the solution for this ticket has been narrowed to: find old URLs. fix old URLs by pointing to existing URLs which probably contain the same or updated content. if no existing URL is available, point it out. speaking of which, I think our help output should really point to https://gnunet.org and not the gnu.org software page? It effectively redirects to gnunet.org anyway. |
|
I like the reference to gnu.org, keeps it symmetric with other GNU packages and stresses our gnu-ishness ;-) Anyway, I think we can close this bug, as 'finding broken URLs' is an eternal task that we can never finish in the current Web architecture ;-) |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-02-22 11:39 | nikita | New Issue | |
2019-02-22 11:40 | nikita | Note Added: 0013942 | |
2019-02-22 11:41 | nikita | Assigned To | => nikita |
2019-02-22 11:41 | nikita | Status | new => assigned |
2019-02-22 11:51 | nikita | Summary | READMEs still point to old gnunet.org => Various files still point to old gnunet.org |
2019-02-22 11:51 | nikita | Description Updated | |
2019-02-22 12:30 | nikita | Priority | high => normal |
2019-02-22 12:31 | nikita | Note Added: 0013943 | |
2019-02-22 12:31 | nikita | Assigned To | nikita => |
2019-02-28 11:49 | Christian Grothoff | Status | assigned => confirmed |
2019-02-28 11:49 | Christian Grothoff | Target Version | => 0.11.1 |
2019-03-15 00:13 | nikita | Note Added: 0014202 | |
2019-03-15 00:14 | nikita | Note Added: 0014203 | |
2019-03-16 18:07 | ic.rbow | Note Added: 0014212 | |
2019-03-16 19:39 | nikita | Note Added: 0014215 | |
2019-03-20 23:48 | nikita | Note Added: 0014224 | |
2019-03-20 23:48 | nikita | Assigned To | => Christian Grothoff |
2019-03-20 23:48 | nikita | Status | confirmed => assigned |
2019-03-20 23:49 | nikita | Note Added: 0014225 | |
2019-04-03 12:16 | Christian Grothoff | Product Version | => Git master |
2019-04-03 12:16 | Christian Grothoff | Target Version | 0.11.1 => |
2019-04-10 13:33 | Christian Grothoff | Note Added: 0014279 | |
2019-04-10 13:33 | Christian Grothoff | Status | assigned => feedback |
2019-04-10 13:33 | Christian Grothoff | Note Added: 0014280 | |
2019-04-10 13:41 | nikita | Note Added: 0014281 | |
2019-04-10 13:41 | nikita | Status | feedback => assigned |
2019-04-10 13:43 | nikita | Note Edited: 0014281 | |
2019-04-10 13:48 | Christian Grothoff | Note Added: 0014282 | |
2019-04-10 13:50 | Christian Grothoff | Note Added: 0014283 | |
2019-04-10 13:52 | nikita | Note Added: 0014284 | |
2019-04-10 13:52 | nikita | Assigned To | Christian Grothoff => nikita |
2019-04-10 13:53 | nikita | Status | assigned => acknowledged |
2019-04-11 13:44 | nikita | Note Added: 0014288 | |
2019-04-20 13:03 | nikita | Note Added: 0014315 | |
2019-04-20 13:03 | nikita | Assigned To | nikita => |
2019-05-02 14:34 | Christian Grothoff | Note Added: 0014371 | |
2019-05-02 14:34 | Christian Grothoff | Assigned To | => Christian Grothoff |
2019-05-02 14:34 | Christian Grothoff | Status | acknowledged => resolved |
2019-05-02 14:34 | Christian Grothoff | Resolution | open => fixed |
2019-05-02 14:34 | Christian Grothoff | Fixed in Version | => 0.11.4 |
2019-05-02 14:34 | Christian Grothoff | Severity | major => text |
2019-05-02 14:34 | Christian Grothoff | Resolution | fixed => not fixable |
2019-05-02 14:34 | Christian Grothoff | Target Version | => 0.11.4 |
2019-05-12 13:29 | Christian Grothoff | Status | resolved => closed |