For some reason, this came to mind when I was thinking about the bodhi link issue but how do we feel about putting a custom 404 on autoqa.fp.o?
Since we don't keep logs forever, anything that links to old results goes to a generic 404 without more explanation than "could not find the file you were looking for". Instead, we could do a custom 404 that contains:
- Explanation of log retention policy - Relevant AutoQA or FedoraQA links
It would involve a small change to the apache config and some static HTML on the autotest server. Pretty easy finger food :)
Thoughts?
Tim
For some reason, this came to mind when I was thinking about the bodhi link issue but how do we feel about putting a custom 404 on autoqa.fp.o?
Since we don't keep logs forever, anything that links to old results goes to a generic 404 without more explanation than "could not find the file you were looking for". Instead, we could do a custom 404 that contains:
- Explanation of log retention policy
- Relevant AutoQA or FedoraQA links
Good idea, this. Maybe include Wiki link amongst the above?
On Mon, 2011-07-11 at 13:57 -0600, Tim Flink wrote:
For some reason, this came to mind when I was thinking about the bodhi link issue but how do we feel about putting a custom 404 on autoqa.fp.o?
Since we don't keep logs forever, anything that links to old results goes to a generic 404 without more explanation than "could not find the file you were looking for". Instead, we could do a custom 404 that contains:
- Explanation of log retention policy
- Relevant AutoQA or FedoraQA links
It would involve a small change to the apache config and some static HTML on the autotest server. Pretty easy finger food :)
Thoughts?
Neat idea. Might be more appropriate for autotest since the namespace for the path that will trigger the 404 is provided by autotest. Either way, a friendlier looking 404 that provides links for the information you highlight couldn't hurt.
Thanks, James
On 07/12/2011 06:12 AM, James Laska wrote:
On Mon, 2011-07-11 at 13:57 -0600, Tim Flink wrote:
For some reason, this came to mind when I was thinking about the bodhi link issue but how do we feel about putting a custom 404 on autoqa.fp.o?
Since we don't keep logs forever, anything that links to old results goes to a generic 404 without more explanation than "could not find the file you were looking for". Instead, we could do a custom 404 that contains:
- Explanation of log retention policy
- Relevant AutoQA or FedoraQA links
It would involve a small change to the apache config and some static HTML on the autotest server. Pretty easy finger food :)
Thoughts?
Neat idea. Might be more appropriate for autotest since the namespace for the path that will trigger the 404 is provided by autotest. Either way, a friendlier looking 404 that provides links for the information you highlight couldn't hurt.
How do you see that working as integrated into Autotest? The basic idea of a custom 404 for results might work but I'm wondering if the concept of a custom 404 page would provide us with more utility if we had FedoraQA specific information in it.
Tim
On Tue, 2011-07-12 at 09:59 -0600, Tim Flink wrote:
On 07/12/2011 06:12 AM, James Laska wrote:
On Mon, 2011-07-11 at 13:57 -0600, Tim Flink wrote:
For some reason, this came to mind when I was thinking about the bodhi link issue but how do we feel about putting a custom 404 on autoqa.fp.o?
Since we don't keep logs forever, anything that links to old results goes to a generic 404 without more explanation than "could not find the file you were looking for". Instead, we could do a custom 404 that contains:
- Explanation of log retention policy
- Relevant AutoQA or FedoraQA links
It would involve a small change to the apache config and some static HTML on the autotest server. Pretty easy finger food :)
Thoughts?
Neat idea. Might be more appropriate for autotest since the namespace for the path that will trigger the 404 is provided by autotest. Either way, a friendlier looking 404 that provides links for the information you highlight couldn't hurt.
How do you see that working as integrated into Autotest? The basic idea of a custom 404 for results might work but I'm wondering if the concept of a custom 404 page would provide us with more utility if we had FedoraQA specific information in it.
I see the case for multiple 404 pages. One where upstream autotest provides one, and then any instances providing their own branded 404. I think your idea fits well with the later ... our instance of autotest (autoqa) providing a Fedora/AutoQA branded 404 page.
Thanks, James
For some reason, this came to mind when I was thinking about the bodhi link issue but how do we feel about putting a custom 404 on autoqa.fp.o?
Since we don't keep logs forever, anything that links to old results goes to a generic 404 without more explanation than "could not find the file you were looking for". Instead, we could do a custom 404 that contains:
- Explanation of log retention policy
- Relevant AutoQA or FedoraQA links
It would involve a small change to the apache config and some static HTML on the autotest server. Pretty easy finger food :)
Great idea. Ticket created
https://fedorahosted.org/autoqa/ticket/354
and proposed to 0.6 milestone.
autoqa-devel@lists.fedorahosted.org
-
James Laska -
John Dulaney -
Kamil Paral -
Tim Flink