What steps will reproduce the problem?
1. Reading Project Home
About: Preferably use the proxy on it's own domain e.g. http://proxy.xyz.com/
WHY? I found no reason to do that.
Path, domain, implementation are not a design question, so it unnecesary to say
the people where to use. It can be used also as php -f script with argv instead
a web interface.
About the comment of the POST and Sessions, Glype and Poxy handles them
perfectly. But, i like your way of that proxy.
I will suggest you to create variants over those 3 methods.
1. Using cURL
2. Using file_get_contents($var, $context)
3. Using server/client sockets.
Sometimes a little script is a really BIG value.
How do need 500Kb script to just bypass a GET connection??
WELL; DONE
Original issue reported on code.google.com by
ErM3...@gmail.comon 4 Mar 2015 at 6:15