You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is, a fix was made in Volto to access images of private content. So we have to go through it. Can we remove the nginx configuration that makes the request directly to the backend?
when we authenticate, the __ac cookie is placed in the browser. This does not occur on a vanilla installation. With the __ac cookie, it is possible for nginx to request images directly from Plone.
When we create a Lead Image block, the Manager cannot see the image in the block until the content is published.
What did I do:
http://localhost
The image is not shown in the block.
In Chrome devtools I see the image request:
http://localhost/news/@@images/2acb7e75-838e-43bd-a686-7d48cfc01d1b.png
But It gets a 302, redirecting to
https://localhost/acl_users/credentials_cookie_auth/require_login?came_from=/news/%40%40images/2acb7e75-838e-43bd-a686-7d48cfc01d1b.png
That is, it is as if the user does not have permission.
In the
nginx
configuration, I see that requests to@@image
are sent directly to the backend, without going through the frontend:plone-frontend/examples/webserver-volto-plone-postgres/default.conf
Lines 30 to 34 in d5078df
It seems that in this situation, either the auth token is not passed to the backend, or the token passed is not valid in this request.
When I remove this configuration, making the request go through the frontend, everything works fine.
The text was updated successfully, but these errors were encountered: