Mat Kelly
Mat Kelly
Ping @ibnesayeed. This PR was submitted a month ago and is awaiting your approval and/or comment.
@akavel I believe this is what already occurs. For example, if I ```sh ipwb index ipwb/samples/warcs/5mementos.warc | ipwb replay ``` then `curl -i http://localhost:5000/20140114100000/memento.us/`, I get an HTTP 200 response,...
> However, this issue can easily be resolved by utilizing warcio which is released under MIT-compatible Apache 2.0 license. That would solve the issue for the WARC-related functions we use...
For the most part, we have moved to using the Apache 2.0-licenses warcio instead of importing parts of the pywb module. An outstanding issue that prevents this ticket from being...
Ok, then the problem is _worse_ than originally reported.
@ibnesayeed I believe we ought to outline the dynamics and some use cases of using a remote IPFS daemon from ipwb.
Related effort/feature suggestion: https://github.com/ipfs-shipyard/ipfs-desktop/issues/602
WACZ files can be interpreted as a ZIP file with a defined structure. The target for ipwb (WARCs) are in `/archive`. Thus, the WACZ file should be read, interpreted as...
Preliminary support added in [779978a](https://github.com/oduwsdl/ipwb/commit/779978ae6480dd5f677c9e5a5a97dbb7c0b3546d). WACZ detection should be improved but importing py-wacz incurs others dependencies due to pywb coupling.
Also, `is_zipfile()` fails on WACZ files due to the magic number (signature) not matching that of a ZIP file.