Bug #6782

Indexes on nightly.tails.boum.org should display complete filenames

Added by sajolida 2014-02-26 19:41:54 . Updated 2018-01-22 12:05:23 .

Status:
Resolved
Priority:
Low
Assignee:
Category:
Infrastructure
Target version:
Tails_3.5
Start date:
2014-02-26
Due date:
% Done:

50%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

On nightly.tails.boum.org, the indexes doesn’t show the complete filenames, since those a quite long. So at first sight, it is not possible to know which file is the ISO, which file the signature, etc.

Setting the NameWidth option of the modindex Apache module might do the trick:

https://httpd.apache.org/docs/2.2/mod/mod_autoindex.html#indexoptions

Files

Screenshot from 2018-01-21 12-55-41.png (45531 B) sajolida, 2018-01-21 12:56:32

Subtasks

History

#1 Updated by intrigeri 2014-02-26 20:01:16

We don’t use Apache, and this does not seem important enough to suffer a webserver switch. I’ve not found any way to do so with nginx. Knowing that, I’d like to downgrade this bug severity to Low, as I don’t see when we would want to put the time in to fix this.

#2 Updated by sajolida 2014-02-27 09:05:13

  • Priority changed from Normal to Low

This problem was reported by a user that I pointed to the UEFI ISO for testing. He was very confused by the layout because the file extension was not displayed. Indeed, unless you know how to look at the link location at the bottom left of your browser, there is no way of knowing what is an ISO and what is an signature file. But maybe that’s no big deal if it is not easy to fix on Nginx.

#3 Updated by Dr_Whax 2014-04-10 21:02:02

I did some research into this, apparently, it’s not in a way we like. We would need to patch the nginx source, not something we might like: http://forum.nginx.org/read.php?2,124400,167420#msg-167420

#4 Updated by intrigeri 2014-04-11 08:50:41

> I did some research into this, apparently, it’s not in a way we like. We would need
> to patch the nginx source, not something we might like:

Indeed, I don’t think we want to use and maintain a locally patched nginx package just to fix this.

#5 Updated by bertagaz 2014-11-17 12:23:57

If really needed, an alternate solution could be to auto-generate ourselves the index.html page, and remove nginx’ autoindex.

That could probably be done at the end of our build script, in a cronjob, or maybe in a dedicated build step.

#6 Updated by intrigeri 2015-01-10 10:40:25

This problem will soon be mitigated by the latest.iso etc. symlinks, introduced with Feature #8518.

#7 Updated by Anonymous 2018-01-19 15:58:27

Looks good to me, should we close this ticket?

#8 Updated by Anonymous 2018-01-19 15:59:11

  • Assignee set to sajolida
  • QA Check set to Info Needed

If you think like me that this is solved, please close this ticket.

#9 Updated by intrigeri 2018-01-19 16:35:30

  • Assignee deleted (sajolida)
  • QA Check deleted (Info Needed)

u wrote:
> If you think like me that this is solved, please close this ticket.

It’s been mitigated as said above but practice has shown that pointing to the directory that contains the symlinks results in useless test reports: neither developpers nor testers can know what was the tested ISO. So we actually point people to the page that still has this bug instead. So this bug is still a problem in theory (I’ve not heard of it myself recently and I do send calls for testing pretty often) but at least we have useful test results.

#10 Updated by sajolida 2018-01-21 13:02:19

It’s definitely not solved. See screenshot: which one is the ISO image?

But, like intrigeri, I’m not sure it’s worth solving it if it doesn’t cause real problems and is complicated to solve. If nothing evolved regarding the possible solutions since Bug #6782#note-3, Bug #6782#note-4, and Bug #6782#note-5. I think we should reject this.

#11 Updated by intrigeri 2018-01-22 09:12:49

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to sajolida
  • Target version set to Tails_3.6
  • % Done changed from 0 to 50
  • QA Check changed from Info Needed to Ready for QA

Fixed by switching to the fancyindex nginx module that was not available 4 years ago when I last looked into this. I’m glad this ticket triaging session prompted me to do an updated web search on this topic :)

And for consistency I did the same for all everything we run that does autoindexing:

Good enough?

I think we’re done as far as this ticket is concerned, but if someone wants to tweak this some more, make the thing responsive and what not:

#12 Updated by sajolida 2018-01-22 12:05:23

  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • Target version changed from Tails_3.6 to Tails_3.5
  • QA Check deleted (Ready for QA)

I love it!!! (and it’s already responsive)