| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
When parsing content to retrieve images to save locally, we only check for the content-type of the image response.
In some case, that value is empty.
Now we’re also checking for the first few bytes of the content as an alternative to detect if it’s an image wallabag can handle.
We might get higher image supports using that alternative method.
|
| |
|
|
|
|
|
|
| |
Images with `&` in the path weren’t well replaced because they might be with `&` in the html instead.
Replacing `&` with `&` fix the problem.
|
|
|
|
|
|
| |
Fixes #2805
Signed-off-by: Kevin Decherf <kevin@kdecherf.com>
|
| |
|
| |
|
|
|
|
| |
This give us ability to use Entry ID to determine where to store images and it’s then more easy to remove them when we remove the entry.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
Needs to rewrite them properly (get base url)
|