[GH-ISSUE #176] Index: Link index recursively shows itself inside the iframe #123

Closed
opened 2026-03-01 14:40:47 +03:00 by kerem · 6 comments
Owner

Originally created by @danmed on GitHub (Mar 14, 2019).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/176

I've just installed and got this working, but have a weird bug.

The first page i archived worked great.. i go to the index page and then click on the text link and it takes me to a nice HTML representation of the page...

Any subsequent links i archive, the text link takes me to the "Link Index" page, but in the iframe underneath is another copy of the same "Link Index" page...

https://imgur.com/a/UJqJDVc

Eg:

First link i archived, the text link (the title of the page) is linked to :
https://*****/ArchiveBox/output/archive/1552560659/linuxconfig.org/allow-ssh-root-login-on-ubuntu-18-04-bionic-beaver-linux.html

Any subsequent archived pages, the text links like this :

https://******/ArchiveBox/output/archive/1552562637/index.html

Originally created by @danmed on GitHub (Mar 14, 2019). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/176 I've just installed and got this working, but have a weird bug. The first page i archived worked great.. i go to the index page and then click on the text link and it takes me to a nice HTML representation of the page... Any subsequent links i archive, the text link takes me to the "Link Index" page, but in the iframe underneath is another copy of the same "Link Index" page... https://imgur.com/a/UJqJDVc Eg: First link i archived, the text link (the title of the page) is linked to : https://*****/ArchiveBox/output/archive/1552560659/linuxconfig.org/allow-ssh-root-login-on-ubuntu-18-04-bionic-beaver-linux.html Any subsequent archived pages, the text links like this : https://******/ArchiveBox/output/archive/1552562637/index.html
kerem 2026-03-01 14:40:47 +03:00
Author
Owner

@danmed commented on GitHub (Mar 14, 2019):

So, a bit more testing.. the problem seems to be that if i send it to a url with an index.html or index.php etc in the actual URL, it works great.. if the URL is just a folder.. then its not and it has this wierd behaviour..

good :
https://tylermade.net/2017/09/14/the-perfect-reverse-proxy-nginx-ssl-webui-management/index.php

bad:
https://tylermade.net/2017/09/14/the-perfect-reverse-proxy-nginx-ssl-webui-management/

<!-- gh-comment-id:472816267 --> @danmed commented on GitHub (Mar 14, 2019): So, a bit more testing.. the problem seems to be that if i send it to a url with an index.html or index.php etc in the actual URL, it works great.. if the URL is just a folder.. then its not and it has this wierd behaviour.. good : https://tylermade.net/2017/09/14/the-perfect-reverse-proxy-nginx-ssl-webui-management/index.php bad: https://tylermade.net/2017/09/14/the-perfect-reverse-proxy-nginx-ssl-webui-management/
Author
Owner

@pirate commented on GitHub (Mar 15, 2019):

Oh yeah I've seen this bug before, I think I know how to fix it. Before I push anything though, do you mind confirming the git commit hash you're running so I can make sure you're on the latest master.

<!-- gh-comment-id:473332538 --> @pirate commented on GitHub (Mar 15, 2019): Oh yeah I've seen this bug before, I think I know how to fix it. Before I push anything though, do you mind confirming the git commit hash you're running so I can make sure you're on the latest master.
Author
Owner

@danmed commented on GitHub (Mar 15, 2019):

Is this what you're after? f0cf1772

<!-- gh-comment-id:473347767 --> @danmed commented on GitHub (Mar 15, 2019): Is this what you're after? f0cf1772
Author
Owner

@pirate commented on GitHub (Mar 19, 2019):

Ok I think I fixed it in 61ec497. Can you try pulling the latest master and giving it a try.

<!-- gh-comment-id:474604614 --> @pirate commented on GitHub (Mar 19, 2019): Ok I think I fixed it in 61ec497. Can you try pulling the latest master and giving it a try.
Author
Owner

@danmed commented on GitHub (Mar 20, 2019):

Hmm i did a "git pull" but the problem is still there and the interface is
still showing " Archive created using ArchiveBox
https://github.com/pirate/ArchiveBox version f0cf1772
https://github.com/pirate/ArchiveBox/commit/f0cf17722b2f047f1bb5d69c6a16736e09c0ea03
"

what have i done wrong here?

On Tue, Mar 19, 2019 at 10:11 PM Nick Sweeting notifications@github.com
wrote:

Ok I think I fixed it in 61ec497
https://github.com/pirate/ArchiveBox/commit/61ec4971e9f2007a1e20e2780b4e857659a3e38f.
Can you try pulling the latest master and giving it a try.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pirate/ArchiveBox/issues/176#issuecomment-474604614,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsuWom_mNIyuKiQ0BlHe0nUULLiJowJks5vYWCGgaJpZM4bz7D5
.

<!-- gh-comment-id:474812729 --> @danmed commented on GitHub (Mar 20, 2019): Hmm i did a "git pull" but the problem is still there and the interface is still showing " Archive created using ArchiveBox <https://github.com/pirate/ArchiveBox> version f0cf1772 <https://github.com/pirate/ArchiveBox/commit/f0cf17722b2f047f1bb5d69c6a16736e09c0ea03> " what have i done wrong here? On Tue, Mar 19, 2019 at 10:11 PM Nick Sweeting <notifications@github.com> wrote: > Ok I think I fixed it in 61ec497 > <https://github.com/pirate/ArchiveBox/commit/61ec4971e9f2007a1e20e2780b4e857659a3e38f>. > Can you try pulling the latest master and giving it a try. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/pirate/ArchiveBox/issues/176#issuecomment-474604614>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ADsuWom_mNIyuKiQ0BlHe0nUULLiJowJks5vYWCGgaJpZM4bz7D5> > . >
Author
Owner

@danmed commented on GitHub (Mar 20, 2019):

Ah nevermind.. looks like i needed to add a link for it to refresh the
page...seems to be working now! thanks!

On Wed, Mar 20, 2019 at 12:43 PM Dan Medhurst danmed@gmail.com wrote:

Hmm i did a "git pull" but the problem is still there and the interface is
still showing " Archive created using ArchiveBox
https://github.com/pirate/ArchiveBox version f0cf1772
https://github.com/pirate/ArchiveBox/commit/f0cf17722b2f047f1bb5d69c6a16736e09c0ea03
"

what have i done wrong here?

On Tue, Mar 19, 2019 at 10:11 PM Nick Sweeting notifications@github.com
wrote:

Ok I think I fixed it in 61ec497
https://github.com/pirate/ArchiveBox/commit/61ec4971e9f2007a1e20e2780b4e857659a3e38f.
Can you try pulling the latest master and giving it a try.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pirate/ArchiveBox/issues/176#issuecomment-474604614,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsuWom_mNIyuKiQ0BlHe0nUULLiJowJks5vYWCGgaJpZM4bz7D5
.

<!-- gh-comment-id:474813450 --> @danmed commented on GitHub (Mar 20, 2019): Ah nevermind.. looks like i needed to add a link for it to refresh the page...seems to be working now! thanks! On Wed, Mar 20, 2019 at 12:43 PM Dan Medhurst <danmed@gmail.com> wrote: > Hmm i did a "git pull" but the problem is still there and the interface is > still showing " Archive created using ArchiveBox > <https://github.com/pirate/ArchiveBox> version f0cf1772 > <https://github.com/pirate/ArchiveBox/commit/f0cf17722b2f047f1bb5d69c6a16736e09c0ea03> > " > > what have i done wrong here? > > On Tue, Mar 19, 2019 at 10:11 PM Nick Sweeting <notifications@github.com> > wrote: > >> Ok I think I fixed it in 61ec497 >> <https://github.com/pirate/ArchiveBox/commit/61ec4971e9f2007a1e20e2780b4e857659a3e38f>. >> Can you try pulling the latest master and giving it a try. >> >> — >> You are receiving this because you authored the thread. >> Reply to this email directly, view it on GitHub >> <https://github.com/pirate/ArchiveBox/issues/176#issuecomment-474604614>, >> or mute the thread >> <https://github.com/notifications/unsubscribe-auth/ADsuWom_mNIyuKiQ0BlHe0nUULLiJowJks5vYWCGgaJpZM4bz7D5> >> . >> >
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ArchiveBox#123
No description provided.