Jump to content

i960

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by i960

  1. Looks like I'll have to wait it out. I've been searching around for ways to do this without curl and I'm coming up totally empty. The only things I've found are scripts like this: http://www.xiven.com/sourcecode/digestauthentication But that is something that goes on the server I am connecting to, not the other way around. FWIW, this is the code I am using: ><? $url = "http://some.url.com"; $ch = curl_init(); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_URL, $url); curl_setopt($ch, CURLOPT_USERPWD, "username:password"); $result = curl_exec($ch); curl_close($ch); echo $result; ?> I've also tried using the following, but this is what requires the newer version of Curl: ><? $return = `/usr/bin/curl -u username:password http://some.url.com --digest`; echo $return; ?> I just can't seem to find anything using PHP that doesn't require Curl. The company I am trying to connect to has never had anyone use PHP to connect before. They have examples using Java, but I know nothing about Java or if it's installed on the server or anything.
  2. Does anyone know how to connect to a server using HTTP Digest Authentication using PHP and without using Curl? The version of Curl currently installed on the server I am on (server 39) is 7.10.5, and HTTP Digest Authentication was not added to Curl until version 7.10.6, and the latest version is 7.10.8. I'm not sure if there are any planned upgrades to the servers anytime soon, but I need to be able to do this asap. Some help would be appreciated. Thanks! Jeff Kieke
  3. Why not just get a resellers account? They are pretty cheap for what you get, and it's really convenient if you have more than one website. I have 6 websites being hosted by TCH with a deluxe resellers account and I couldn't be happier. http://www.totalchoicehosting.com/web-host...-resellers.html
  4. A better way to do that table fakeout thing would be to use CSS to put the image in the background. Not only would it be standards compliant (the above code isn't), it would make it a little harder for them to find the source of the image since the path would be in a separate css file as opposed to being in the html. Of course, it's still not really effective since they can do a screen capture like Deverill said. All it's going to do is stop the thieves who are lazy or otherwise don't really know what they are doing. Kinda like the steering wheel club... a few seconds with a hack saw and you can cut through the steering wheel itself and rip that thing out of there. It'll just slow down the amatures. Your best bet is a lawyer.
×
×
  • Create New...