Closed Clevero closed 9 years ago
1st is just not necessary plus I would like to avoid putting too much PHP code inside the templates. 2nd would make SSL proxies less secure, it should load https version of url_form.js on SSL proxies and http version on non-SSL proxies to reduce CPU on php-proxy.com side. Having // automatically loads the right version.
to second: i don't know about that fact :) but why is the js file on another server and not like the proxy files on the side of the user-server? every time the file loads, you have the ip of the proxy and you can see how many times, the proxy is in use i dont't know, but isn't that a security problem for the user-server if he don't want to be tracked?
The idea was to put most of the proxifying/parsing logic inside one global js file so if YouTube decides to change their layout, a update could be deployed immediately by just updating this one js file instead of forcing everyone to go back to php-proxy.com and download a new proxy version like they would have to do now with Glype.
remove http:// in the url form if we have just a non encrypted http connection (for beauty and better readableness purposes
or is it better if we make in the config.php such setting?