Baseflow / Baseflow/flutter_cache_manager

Cache 204 - No content

Abierto
#333 7 comentarios 0 reacciones 0 asignados Ver en GitHub
type: enhancement
Lenguaje dominante
Dart
Estrellas
809
Forks
510
Merge medio
6 min
PR fusionados (30 d)
1

Descripción

## 💬 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?

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
dart
Área
mobile-dev, performance
Tipo de issue
Nueva funcionalidad
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.