So open_basedir settings are mucking with curl's CURLOPT_FOLLOWLOCATION? That seems pretty whack to this naive reader... Guess you are stuck reading the headers and doing as many more curl_exec()s on the Location: as it takes. On Mon, March 19, 2007 5:15 am, Mathijs wrote: > Jochem Maas wrote: >> Mathijs wrote: >>> Hello there, >>> >>> I Need a bypass to have followlocation working while open_basedir >>> is in >>> affect. >>> >>> I Don't see why we can't enable/disable this protection by our >>> selfs >>> when needed. >> >> we can't see past the choices we don't understand though can we? >> >>> Keep the protection enabled by default, and let the ppl disable it >>> if >>> they realy want to. >> >> well you go and code the routines that make that work without >> completely >> raping any form of security that is currently offered by >> open_basedir - put another >> way: if it was that easy someone would have done it by now. >> >>> Anyway, how can i bypass this the easy way. >> >> add the symlinked location to the the open_basedir directive?? >> >>> Thx in advanced. >>> > > Well it is an HTTP site where the re-location come's from. > And it is very irritating when i need to do the header locations my > self. > > But if there is no setting i can change i think i need to do it my > self. > a shame that this can't be fixed on an easy way. > > Thx anyway :). > > Regards, > Mathijs. > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some starving artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
