Digital Point Image Proxy

Digital Point Image Proxy [Paid] 1.0.4

No permission to buy ($75.00)
Overview Updates (4) Reviews (2) History Discussion
Shawn I know with only less than a week of free time left it might not be possible, but would this addon be able to whitelist, exclude 3rd party referenced urls which already are served via https:// so they don't get proxied and only proxy non-https ?

thanks
 
  • Like
Reactions: rdn
Nah, it's for more than just making a green lock in your browser.

Doing something like that would render it useless for stopping malware warnings and cookie stuffing.
 
How can I get this to work with my current CDN?

Like images load on the threads like this: www.domain.com/proxy/[Random Image ID Crap]/image.png
Is there a way to make them load from cdn.domain.com/proxy/[Random Image ID Crap]/image.png ?

I tested the url in the browser and it works fine. However just need it to get working like that and have the images load from the cdn.
 
I installed ImageProxy plugin on my Xenforo site but still got mixed content issue over HTTPS. Are there any other configurations I need to do?
 
Does this work for XenForo 1.4?

Solved, it's in the core (Image and link proxy)
 
Last edited:
@digitalpoint just updated to 1.0.4 and re-enabled on my forums but I get 404 errors with your addon enabled every since I upgraded to PHP 5.6 (currently on PHP 5.6.6). not sure if it's related to url length

for example when addon enabled image url with 404 error is like
Code: 
/proxy/2gXUhj2x4UUlPixjo8ijBKkAkmo5T64D3q%2FfCZC%2FTKNSHxbj%2BDZmajiWwLRk6nOPHjZk8hhGcRqTyx3NRm53zLTA1Ujw441QWbQMqjEGa%2FZLXprobwzTTxOTF7VPNcMgwjgH%2BkMC0eiszTVO2S2XRJsurT7i5%2BHBj%2BuJKY2bJ75LOtvdXFzA9ly5A7V27N5IOg%3D%3D/image.png

with default XF image proxy it's fine and shows image okay at https://community.centminmod.com/threads/testing-image-proxying.213/
 
Last edited:
Is the error coming from the web server or the application (XF)? If it's coming from the web server, you probably have your web server intercepting .png files and not passing it to the application (regardless if they exist or not). You can test it by trying to go to the proxy URL without the .png extension... in the above example, it would be:

Code: 
/proxy/2gXUhj2x4UUlPixjo8ijBKkAkmo5T64D3q%2FfCZC%2FTKNSHxbj%2BDZmajiWwLRk6nOPHjZk8hhGcRqTyx3NRm53zLTA1Ujw441QWbQMqjEGa%2FZLXprobwzTTxOTF7VPNcMgwjgH%2BkMC0eiszTVO2S2XRJsurT7i5%2BHBj%2BuJKY2bJ75LOtvdXFzA9ly5A7V27N5IOg%3D%3D/image

If that URL works, when your web server is intercepting the request because it has a .png extension and not passing it to XenForo.

Sometimes people have web servers configured to intercept "static" files by extension without actually checking if they exist or not. And never hand off the request to the application.
 
yeah i use ngx_pagespeed which auto optimises and rewrites image extensions on the fly https://community.centminmod.com/threads/benefits-of-ngx_pagespeed.1032/

with PHP 5.5 and your image proxy 1.02, all was working fine with ngx_pagespeed auto optimising detected images with specific extensions.

it didn't work once i updated to PHP 5.6 with 1.02 or 1.04.

reason why i choose your addon was it served proxied images via non .php /proxy/ so ngx_pagespeed could pick up proxied images for auto optimisation
 
I'm not sure what would affect it with PHP 5.6... I use 5.6 on my servers without any issues (but I don't use ngx_pagespeed... so maybe the combo of the two somehow?)

If you want to just get rid of the extension with the addon, you can get into the
DigitalPointImageProxy/Route/Prefix/Proxy file, and comment out the following line:
PHP: 
$extension = 'png';

It's really only there to allow CDNs that cache based on extension to cache the images at their local data center and serve from there (for example CloudFlare). Serves no other purpose what-so-ever, so if you don't care about that, it's no loss to comment it out.

A possibly better solution long term would be to maybe have ngx_pagespeed only kick in if the file it's processing actually exists on the server.
 
well i need the image extension .png as ngx_pagespeed does it's work when it detects .png it auto converts it to webp if browser supports it

but i disabled ngx_pagespeed via tagging ?PageSpeed=off onto my url as well as at pagespeed.conf level disallowed the proxy

Code: 
pagespeed Disallow */proxy/*;

just to see if taking ngx_pagespeed out of the equation helps, but didn't.

also removed all my static file match on .png from my vhost as well but didn't help

I'll keep messing with my config and see what turns up as I love to get back to how it was performing with your addon + ngx_pagespeed :D
 
I thought about it a little more, I think it has to be coincidental that it started not working with PHP 5.6... like I said, I use PHP 5.6 myself, but also... if the error you are getting is a normal Nginx 404, it would mean Nginx is never passing it along to the application (because a 404 from XF looks different). And if it's never passing it along to the application, it would never be hitting php-fpm, at which point the version should be irrelevant since it never makes it far enough to get to PHP.
 
You must log in or register to reply here.
Back
Top Bottom