-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
picture not diplay normally #667
Comments
@notfresh You can check as follows.
|
@LinkinStars the image can't be visited from brower, it redirect to another page with a tip 403 I use
which was too old and not match the image error I run docker deamon and docker container with the only user root. |
@notfresh This issue has been asked before. FYI: #502 (comment) |
@LinkinStars I have aquestions: Why does the picture I set as my avatar which I upload could show on the web page normally? As you said in the #502 issue, the problem could be settled with domain name , but why the avatar could show normlly IN IP VISIT MODE ? Is there any authentication mechanism to block the picture by ip visit but no such a check on avatar? I have logged in the brower and with cookie open |
@notfresh Thank you for your question. Yes, the two have different validation rules. Since avatars may come from different sources such as gravatar. So it is currently left open for avatars. Since the essential aspect of this requirement is actually that we don't want the content of the user's question or answer to be posted somewhere else in private mode. Surely, we will consider your point about private access for avatars though. |
So, this is a bug?, there is another way to solve it?, and keep the setting as "login required=true"? |
Turning off |
Configuring and using a domain can solve this problem. |
I'm using a domain (https + valid cert). Problem persists. |
@upcc-jesse Thanks for the feedback. Is there an error log for this? Actually, the error |
Interestingly it's first a HTTP 302 response when trying to fetch the picture, which redirects to the 403 page. I'm guessing this is just a quirk of how the server handles 40x errors? No logs are generated - in fact, the application generates very few logs overall, even with |
@upcc-jesse Please confirm two issues. The first is whether cookies are allowed in your browser, or whether the problem is the same in other browsers. The second is whether the image can be opened by accessing the image address url directly. Thanks. |
The image cannot be accessed directly in the browser. It working in a Firefox private session appears to point at something being cached or in a cookie. With this new info I went to Firefox's Developer Tools (F12) -> Storage and deleted everything from this tab - specifically cookies, but there was also data in Local Storage and Session Storage. Images now load as expected. Thanks for your help troubleshooting. |
Describe the bug
The picture in comment not display normally
To Reproduce
Steps to reproduce the behavior:
docker run -d -p 9080:80 -v answer-data:/data --name answer apache/answer:latest
Expected behavior
The image shows normally
Screenshots

Platform (please complete the following information):
LSB Version: core-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 20.04.6 LTS
Release: 20.04
Codename: focal
The text was updated successfully, but these errors were encountered: