Removing .php extension from proxy.php images ?

[eva2000]

Sort of related to https://xenforo.com/community/threa...oxy-to-slow-origin-servers.81774/#post-818153

Suggestion:

For Xenforo default image proxy url to be customised without the .php extension i.e. /proxy/ instead of /proxy.php similar to Digitalpoint's proxy image addon which serves proxied images from /proxy/image https://marketplace.digitalpoint.com/image-proxy.2306/item and maybe also make the proxy timeout adjustable within admin.php

Why

1. Seems to alleviate issues reported at https://xenforo.com/community/threads/how-sensitive-is-the-image-proxy-to-slow-origin-servers.81774/ for broken images
2. I use Nginx with ngx_pagespeed module for better performance and pagespeed can't optimise proxy.php served images and auto convert to webp format using Xenforo default proxy image feature. While pagespeed can if the proxied images were served via /proxy/image without the .php extension - see benefits at https://community.centminmod.com/threads/benefits-of-ngx_pagespeed.1032/.

broken images served via Xenforo default image proxy

 

[dethfire]

I don't think they are doing anything other than bug fixes these days

 

[Amaury]

And you know this how?

 

[dethfire]

And you know this how?

Given everything since 1.5 has been a security or bug fix champ

 

[Amaury]

That doesn't mean they're not looking at or implementing suggestions. Perhaps they're implementing them in XenForo 2.0. We don't know, so just be patient.

 

[dethfire]

That doesn't mean they're not looking at or implementing suggestions. Perhaps they're implementing them in XenForo 2.0. We don't know, so just be patient.

That is what I am getting at. It won't be introduced in 1.5

 

[Brent W]

We have over 350,000 images cached in the proxy system and are using Cloudflare. Would be really nice to have those images served by Cloudflare rather than our server after cached.

 

[Brent W]

I just used CloudFlare page rules to "cache everything" from www.example.com/forum/proxy.php?image=* and checking the headers confirmed it worked great; it offloaded more than 70% of my bandwidth to CF and reduced CPU usage by 15-20%.

Unfortunately, I had to ditch CF due to reliability issues (users reporting bogus 502/504 errors daily, no help from CF support). Not sure how you guys are able to use it.

Can anyone confirm this is working?

 

[DeltaHF]

It was a fairly straightforward configuration; I'm not sure why it wouldn't still work.

If I ever re-enable CloudFlare, it's definitely something I would enable again.

 

[Teapot]

I can definitely confirm that image proxy caching is working for us with a basic page rule:



We're using the following settings:

 

[Brent W]

Can anyone confirm this is working?

You can tell when I setup the page rule.

 

[Gossipy]

I can definitely confirm that image proxy caching is working for us with a basic page rule:

View attachment 144280

We're using the following settings:

View attachment 144281

Why are you only caching for one day?

 

[Teapot]

Why are you only caching for one day?

To prevent the cache getting stale if the image proxy has updated. I've since upped it to 5 days for both values, though.