Replies: 2 comments
-
Hi @ghnp5 Thanks for this, I have raised this internally for conversation. Since this is not a bug and more a feature request I have adjusted the tags |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks! No problem. Another suggestion could be to simply add an "expires" header to the responses, to "now" date, or a date in the past. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Before you start please confirm the following.
Problem Description
Portainer doesn't seem to be getting the latest logs for an Nginx container.
Actually - I've just realized what it was.
I had already prepared a very detailed bug report, but I see the problem is that I enabled a default "expires" entry in Nginx, and that's why the logs aren't updating.
It's because the "logs" GET request that Portainer calls is returning the last cached request.
I see the mimetype is
application/vnd.docker.raw-stream
, which I'm going to add to the exceptions.But here's a suggestion -- you could add an extra parameter to the query string, with a timestamp + random number, e.g.
&r=13458151548753
, to ensure this never happens, even if there is a misconfiguration in the server.Thanks!
Portainer version
2.25.1
Portainer Edition
Community Edition (CE)
Platform and Version
Docker 26.1.3
OS and Architecture
AlmaLinux 8
Browser
Firefox
What command did you use to deploy Portainer?
docker-compose.yml
Beta Was this translation helpful? Give feedback.
All reactions