[GH-ISSUE #193] Archiving images fails on some URLs #142

New issue

Closed

opened 2026-02-25 23:33:32 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 23:33:32 +03:00

Owner

Originally created by @tomas on GitHub (Oct 7, 2019).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/193

For some reason when adding this url with the "Archive" option set to true it doesn't store the images. Looks like the server disallows hotlinking, so that may be the issue (havent tested though).

Originally created by @tomas on GitHub (Oct 7, 2019). Original GitHub issue: https://github.com/go-shiori/shiori/issues/193 For some reason when adding [this url](http://www.extentofthejam.com/pseudo/) with the "Archive" option set to true it doesn't store the images. Looks like the server disallows hotlinking, so that may be the issue (havent tested though). ![image](https://user-images.githubusercontent.com/10574/66332895-2c158d00-e90c-11e9-9db1-7fd10b7a23d0.png)

kerem

2026-02-25 23:33:32 +03:00

closed this issue
added the
note:fixed?
label

kerem commented

2026-02-25 23:33:33 +03:00

Author

Owner

@RadhiFadlillah commented on GitHub (Oct 9, 2019):

Hi @tomas

This should be fixed by commit a3e156 thanks to the new web archiver. I also added fix to make sure archive rendered as UTF-8.

@RadhiFadlillah commented on GitHub (Oct 9, 2019): Hi @tomas This should be fixed by commit [a3e156](https://github.com/go-shiori/shiori/commit/a3e1563dff7aeaba97c3984fc7a3bd66743423eb) thanks to the new [web archiver](https://github.com/go-shiori/warc). I also added [fix](https://github.com/go-shiori/shiori/commit/0bc1b4a4cc39426769c07e3b69b2d1e568882a63) to make sure archive rendered as UTF-8. ![Screenshot_2019-10-09_21-02-59](https://user-images.githubusercontent.com/6129042/66488554-4c924280-ead8-11e9-87d0-efdd596bc0ee.png)

kerem commented

2026-02-25 23:33:33 +03:00

Author

Owner

@RadhiFadlillah commented on GitHub (Oct 16, 2019):

Since this issue should've been fixed now, I will close this issue. Feel free to reopen it if needed.

@RadhiFadlillah commented on GitHub (Oct 16, 2019): Since this issue should've been fixed now, I will close this issue. Feel free to reopen it if needed.