29 Aug
2019
29 Aug
'19
3 p.m.
Hi,
is there any chance the list admins could copy the pipermail archive
from lists.ceph.com over to lists.ceph.io? It seems to contain an awful
lot of messages referred elsewhere by their archive URL, many (all?) of
which appear to now lead to 404s.
Example: google "Set existing pools to use hdd device class only". The
top hit is a link to
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-August/029078.html:
$ curl -IL
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-August/029078.html
HTTP/1.1 301 Moved Permanently
Server: nginx/1.10.3 (Ubuntu)
Date: Thu, 29 Aug 2019 12:48:13 GMT
Content-Type: text/html
Content-Length: 194
Connection: keep-alive
Location:
https://lists.ceph.io/pipermail/ceph-users-ceph.com/2018-August/029078.html
Strict-Transport-Security: max-age=31536000
HTTP/1.1 404 Not Found
Server: nginx
Date: Thu, 29 Aug 2019 12:48:14 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 3774
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Vary: Accept-Language, Cookie
Content-Language: en
Or maybe this is just a redirect rule that needs to be cleverer or more
specific, rather than the apparent catch-all .com/.io redirect?
Cheers,
Florian
30 Aug
30 Aug
3:46 p.m.
Yes I’m having the same problem - resorting to cached pages by Google for the time being!
br,
Danny
On 29 Aug 2019, at 14:00, Florian Haas
<florian(a)citynetwork.eu> wrote:
Hi,
is there any chance the list admins could copy the pipermail archive
from lists.ceph.com over to lists.ceph.io? It seems to contain an awful
lot of messages referred elsewhere by their archive URL, many (all?) of
which appear to now lead to 404s.
Example: google "Set existing pools to use hdd device class only". The
top hit is a link to
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-August/029078.html:
$ curl -IL
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-August/029078.html
HTTP/1.1 301 Moved Permanently
Server: nginx/1.10.3 (Ubuntu)
Date: Thu, 29 Aug 2019 12:48:13 GMT
Content-Type: text/html
Content-Length: 194
Connection: keep-alive
Location:
https://lists.ceph.io/pipermail/ceph-users-ceph.com/2018-August/029078.html
Strict-Transport-Security: max-age=31536000
HTTP/1.1 404 Not Found
Server: nginx
Date: Thu, 29 Aug 2019 12:48:14 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 3774
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Vary: Accept-Language, Cookie
Content-Language: en
Or maybe this is just a redirect rule that needs to be cleverer or more
specific, rather than the apparent catch-all .com/.io redirect?
Cheers,
Florian
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
9:39 p.m.
A better course of action would be to copy the "mbox" file(s) that Mailman
uses to archive all messages which pass through any mailing list that it
runs, and then use Mailman "arch" command to regenerate the archives
in the new location -- that way all of the links on the archive pages
themselves will point to the right places. One of the nice things about
"arch", by the way, is that it's cumulative -- by which I mean that it
can handle generating archives from an older mbox file (say, from
a mailing list's previous location) that integrate with archives from
a current mbox file (from a mailing list's current location). Anyway,
I think doing this plus installing redirects from the old location
would probably come close to solving the 404 problem.
If the keepers of the ceph-* mailing list need a hand with this,
please drop me a line.
---rsk
4:11 p.m.
Yes I’m having the same problem - resorting to cached pages by Google for the time being!
br,
Danny
On 29 Aug 2019, at 14:00, Florian Haas
<florian(a)citynetwork.eu> wrote:
Hi,
is there any chance the list admins could copy the pipermail archive
from lists.ceph.com over to lists.ceph.io? It seems to contain an awful
lot of messages referred elsewhere by their archive URL, many (all?) of
which appear to now lead to 404s.
Example: google "Set existing pools to use hdd device class only". The
top hit is a link to
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-August/029078.html:
$ curl -IL
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-August/029078.html
HTTP/1.1 301 Moved Permanently
Server: nginx/1.10.3 (Ubuntu)
Date: Thu, 29 Aug 2019 12:48:13 GMT
Content-Type: text/html
Content-Length: 194
Connection: keep-alive
Location:
https://lists.ceph.io/pipermail/ceph-users-ceph.com/2018-August/029078.html
Strict-Transport-Security: max-age=31536000
HTTP/1.1 404 Not Found
Server: nginx
Date: Thu, 29 Aug 2019 12:48:14 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 3774
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Vary: Accept-Language, Cookie
Content-Language: en
Or maybe this is just a redirect rule that needs to be cleverer or more
specific, rather than the apparent catch-all .com/.io redirect?
Cheers,
Florian
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io
3 Sep
3 Sep
6:29 p.m.
Hi,
replying to my own message here in a shameless attempt to re-up this. I
really hope that the list archive can be resurrected in one way or
another...
Cheers,
Florian
On 29/08/2019 15:00, Florian Haas wrote:
Hi,
is there any chance the list admins could copy the pipermail archive
from lists.ceph.com over to lists.ceph.io? It seems to contain an awful
lot of messages referred elsewhere by their archive URL, many (all?) of
which appear to now lead to 404s.
Example: google "Set existing pools to use hdd device class only". The
top hit is a link to
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-August/029078.html:
$ curl -IL
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2018-August/029078.html
HTTP/1.1 301 Moved Permanently
Server: nginx/1.10.3 (Ubuntu)
Date: Thu, 29 Aug 2019 12:48:13 GMT
Content-Type: text/html
Content-Length: 194
Connection: keep-alive
Location:
https://lists.ceph.io/pipermail/ceph-users-ceph.com/2018-August/029078.html
Strict-Transport-Security: max-age=31536000
HTTP/1.1 404 Not Found
Server: nginx
Date: Thu, 29 Aug 2019 12:48:14 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 3774
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Vary: Accept-Language, Cookie
Content-Language: en
Or maybe this is just a redirect rule that needs to be cleverer or more
specific, rather than the apparent catch-all .com/.io redirect?
Cheers,
Florian
6:42 p.m.
On Tue, Sep 3, 2019 at 6:29 PM Florian Haas <florian(a)citynetwork.eu> wrote:
Hi,
replying to my own message here in a shameless attempt to re-up this. I
really hope that the list archive can be resurrected in one way or
another...
Adding David, who managed the transition.
Thanks,
Ilya
5 Sep
5 Sep
8:40 p.m.
On 03/09/2019 18:42, Ilya Dryomov wrote:
On Tue, Sep 3, 2019 at 6:29 PM Florian Haas
<florian(a)citynetwork.eu> wrote:
It looks like the archives are available again at the original location.
Thank you, this will help a lot of people!
Cheers,
Florian
Hi,
replying to my own message here in a shameless attempt to re-up this. I
really hope that the list archive can be resurrected in one way or
another...
Adding David, who managed the transition.
Thanks,
Ilya
1692
days inactive
1699
days old
7 comments
5 participants
participants (5)
-
Danny Abukalam -
Danny Abukalam -
Florian Haas -
Ilya Dryomov -
Rich Kulawiec