Why are browser caching headers are not sent? #2502
-
|
Neither in curl nor in the browser caching headers are sent: martin:
image: ghcr.io/maplibre/martin
container_name: omniviv-martin
restart: unless-stopped
volumes:
- ./data//mbtiles:/mbtiles:ro
- ./data//fonts:/fonts:ro
- ./data//sprites:/sprites:ro
command: /mbtiles --font /fonts
networks:
- rp
labels:
traefik.docker.network: rp
traefik.enable: true
traefik.http.routers.omniviv-martin.rule: Host(`omniviv-tiles.localhost`)
traefik.http.routers.omniviv-martin.entrypoints: web
traefik.http.routers.omniviv-martin.service: omniviv-martin
traefik.http.services.omniviv-martin.loadbalancer.server.port: '3000'
traefik:
image: traefik:v3
container_name: omniviv-traefik
restart: unless-stopped
command:
- --providers.docker=true
- --entrypoints.web.address=:80
networks:
- rp
ports:
- 80:80
volumes:
- /var/run/docker.sock:/var/run/docker.sock:roSending to port, not through traefik |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
We don't know what the browser caching headers should be. How would we know which headers you want? I have not invested time in how this should work.
|
Beta Was this translation helpful? Give feedback.
We don't know what the browser caching headers should be.
We set an etag, that is sort of an caching header, but not really.
How would we know which headers you want?
-> We currently have no way of knowing what you want in this case, so are not ataching any.
I have not invested time in how this should work.
-> To add this, the first step would be a design issue on how such a feature should work.
Aka, which things should be configurable how.
For example