Glype Proxy 1.1
Glype Proxy (current version 1.1) is an easy-to-use, light-weighted, but great still proxy script written in PHP. You can find other scripts on the internet as well, such as PHProxy (project halted on 2007-09-07). However, Glype is likely to be the only one that is still under development (Glype 2.0) and has probably the largest group of users/coders.
I have been using Glype for my own proxy site on Godaddy free hosting for a while. In the following, I will show you briefly how to do it, as well as the solutions to some problems that I’ve encountered.
The installation of Glype 1.1 is fairly easy, thus you shall not have a problem with that.
In general, you should upload the contents in the /upload directory to the root proxy folder on your server. Upload the files in the /extra folder to the root proxy folder as well (and not the directory itself) if you wish to customize your proxy.
Use http://your_proxy_server/admin.php to access the control panel.
The current version of Glype comes with a default plugin (/plugins/facebook.com.php) for Facebook. Ironically, the latter seems to be the very origin of a common XML error which holds you back from visiting the site.
One solution is to simply remove the file from your server (or to rename it if you want), that is, the proxy works better without it. Since I do not have a Facebook account, I have no means to verify the possible consequences related to this operation, and I’ll be very grateful if you can carry out the test for me (via my proxy or not).
This one is a little bit tricky.
To begin with, it seems that the plugins are rendered useless every time YouTube makes a change. But there’s nothing to be worry about as new plugins would be made available pretty soon, all you need to do is to keep an eye on the forum.
You can easily find posts that offer handy solutions (i.e. plugins) based on Flowplayer, the installation of which is usually done with a single upload operation.
Now you are prepared to offer your YouTube-able proxy service, just make sure that you (and your users) have the encode URL and the encode page option disabled in the control panel. This is not true however, if you are running a Windows server where you are most likely to bumy into another 200 stream not found error before getting things going. The error is, in most cases, caused by the fact that Microsoft IIS 6.0 (7.0) needs a MIME type to recognize the FLV files as streamed media.
A solution is posted here which requires you to change your server configuration via the IIS Manager, but if you are running your proxy on a virtual host (like me), you will need to do that in a different way.
Create (or edit if you have one already) a web.config file in your account’s root directory which includes:
<mimeMap fileExtension=”.flv” mimeType=”video/x-flv” />
A complete list of MIME types that can be added (Godaddy) is listed here in case of necessary.
To use it, you need to enter the following information.
id = proxyuser
pwd = [hide 2] ilovetao [hide 2]
5. Known issues
As far as I am concerned, three last problems remain to be solved.
1. If you are hosting your WordPress in the root folder, the dashboard will sometime behave abnormally (the visual editor in particular) once the above web.config file is added (that is of course, to the same root folder). I have posted on the support forum, but has by far received no answer.
2. You will not be able to play the YouTube videos hosted on the VEVO channel.
3. Glype doesn’t proxy flash applications.