Skip to content

Path marked as loaded even if the result is DISABLED #136

@susanu

Description

@susanu

Hi guys,

Seems that if you call basset on the same path more than once, it marks the path as loaded even if the result is disabled.
Example url: https://www.gravatar.com/avatar/a3a2e97ccd20ce09e1e0049da479c073.jpg?s=80&d=blank&r=g

First call returns DISABLED and use the original url https://www.gravatar.com/avatar/a3a2e97ccd20ce09e1e0049da479c073.jpg?s=80&d=blank&r=g
Second call returns LOADED and use an internal url which doesn't exist https://example.com/storage/basset/www.gravatar.com/avatar/a3a2e97ccd20ce09e1e0049da479c073.jpg

I think you should not mark the path as loaded if the file is not internalized.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

No status

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions