Fri, Dec 6
The first part seems wrong indeed.
Thu, Dec 5
Wed, Dec 4
Tue, Dec 3
Mon, Dec 2
Fri, Nov 29
Wed, Nov 27
Indeed, the History button should be disabled for the empty snapshot case.
Tue, Nov 26
Mon, Nov 25
Thu, Nov 21
Wed, Nov 20
Fri, Nov 15
The Referer checking stuff is built-in to Django's CSRF protection, and I don't think we should disable it.
Actually, this is Django normal behavior regarding CSRF validation, quoting its documentation:
In addition, for HTTPS requests, strict referer checking is done by CsrfViewMiddleware. This means that even if a subdomain can set or modify cookies on your domain, it can’t force a user to post to your application since that request won’t come from your own exact domain.
This is an expected behaviour as https://archive.softwareheritage.org/save/ links to the HTML form to submit a save request, this is not an api endpoint.
Thu, Nov 14
Wed, Nov 13
Ack. I will change the task priority to normal as it is not a critical issue.
Submitted to libmagic: https://bugs.astron.com/view.php?id=123
Sounds like a bug in libmagic, this file is valid UTF-8.
Hopefully, the text/plain mimetypes are usually correctly displayed (see this file for instance).
Tue, Nov 12
Nov 5 2019
This has now been deployed in all components as well as in production databases. Bye bye origin['type'].
Oct 29 2019
Oct 28 2019
Oct 24 2019
Oct 22 2019
Closing this as time for experiments is over.
Oct 21 2019
@anlambert thanks for the detailed explanation !
In fact, the feature you are looking at is already implemented and deployed. You have to select the Take a new snapshot entry from the Actions menu.
However, I agree this action should be visible without having to open a drop-down menu.