Baseflow / Baseflow/flutter_cache_manager

Cache 204 - No content

Offen
#333 7 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
type: enhancement
Vorherrschende Sprache
Dart
Sterne
809
Forks
510
Ø Merge
6 Min.
Gemergte PRs (30 T.)
1

Beschreibung

## 💬 Questions and Help

If I understand the code correctly currently only 200 and 202 status codes are added to the cache.

https://github.com/Baseflow/flutter_cache_manager/blob/c7881776325441f3900277499615981c40d12284/flutter_cache_manager/lib/src/web/web_helper.dart#L23-L24

In my case I have a image API endpoint which *tries* to generate a image/logo/etc. based on a user-provided website URL. Since the user input could just as well be an internal URL or just broken, it is perfectly fine for the endpoint to return a 404 response. Right now this is not cached on the client side but requested every time.

Is this the intended behavior, or any way to cache non-existent URLs?

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Read lib/src/web/web_helper.dart at the linked lines to confirm which HTTP status codes are currently cached. Clarify whether the requested behavior covers 204, 404, or other non-success responses, then verify that the selected behavior prevents repeated requests for the reported image API case.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
dart
Bereich
mobile-dev, performance
Issue-Typ
Feature
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.