ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I thought of that keefaz, but I read the documentation of fopen and believe that opening a URI depends on the PHP.ini settings doesn't it? That is, if the fopen is not allowed to open URI resources then it will return an error. Again, in my shared host, I cannot possibly change the PHP.ini settings, so if that option is disabled then I'm stuck no?
I wanted a more "compatible" solution, but I guess your idea is quite good. I will use it as a last resort, thanks!
It seems to work OK for basic URLs, but when it gets into the CGI parsing, the URL always passes, even for something like "http://www.foo.com/script.pl?alpha", which I'm pretty sure isn't valid. It probably has to do with those zero-width lookbehind thingies that I don't quite understand.