-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
ExternalProxy not displaying certain images. #326
Comments
Ahh, okay. Looking into the code and understanding the error better. We are making the |
Could you try with 2.14.3? |
Oh, this is my fault. I missed updating the versions in the ticket. I took a very cursory look at the code and it seems that the proxy does not strip white space in the URI. This did fix the error I posted above, but now the redirect seems to fail at the regex check in https://github.com/the-djmaze/snappymail/blob/master/snappymail/v/0.0.0/app/libraries/snappymail/http/response.php#L81 |
Also, Just for more clarity. The images that are trying to be resolved and failing are being redirected. Original URL: URL after White Space Replace: This returns the following relevant location header: |
I made some changes, you can try with https://github.com/the-djmaze/snappymail/releases/tag/v2.15.0 |
Brilliant. 2.15.0 Solved this. |
Your welcome! |
Describe the bug
When I have "use local proxy for images" enabled, some images do not display.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expecting proxy to load images.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Mobile (please complete the following information):
not tested on mobile, but since this is a php error, I am sure it will be the same.
Additional context
This is strange because images from that same domain, in the same email displays, but two of them don't. It looks like this might be a type mismatch thing. I don't think the proxy handles the png/gif redirect change very well.
I have been researching this issue and I believe it's related to #16
The text was updated successfully, but these errors were encountered: