Looking for an Extension? Have an Extension request? Post your request here for help. (Note: This forum is community supported; while there is an Extensions Development Team, said team does not dedicate itself to handling requests in this forum)
Static resources (images/CSS/JS) are currently served from the same server where phpBB resides. The problems it creates:
* Extra load on the app server that could be moved to another server.
* Cookie info is sent on every request and it surely not needed.
The extension should enable providing paths for the static resources and these could reside on other servers. For example, I may want to have phpbb running on forum.example.com and serve all my static resources from static.example.org
I wouldn't call it that as the other server may not be a CDN and many use CDNs without changing links but by changing their DNS records. I think a "Path for static files" should be good or simply allowing a full path in the images directory (and additionally CSS/JS directories) rather than a relative one.
Perhaps I am missing something here but if you are serving all the files what is the advantage of having "static" files on one server and "non static" on another? I would actually think that performance could be made worse as calling two servers would add an overhead and if the servers were not synchronised then you could have the data being rendered in the wrong order.
Now if you were to be taking about caching "static" files then that may well be a different issue but my understanding is that most "static" resources are cached either by phpBB and/or the browser. There have been several discussions on these fora about using the likes of Cloudflare to do additional caching - sometimes with success and other times creating additional problems.
David Remember: You only know what you know and - you don't know what you don't know!
I now no longer support any of my extensions but they will start to become available here
Serving static resources from a different server has the following advantages:
1/ Browsers usually limit the number of connection per server so it's faster to serve from different ones.
2/ When logged in you send cookies on every HTTP request. If static resources r on another server, this isn't needed so a bit less communication.
3/ Depending on your server configuration, a server dedicated to static files doesn't need PHP installation.