[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

http://1.1 500 internal server error

   Hi Scott,
   I looked into the EXAMPLE7, for my webservice I used the http_url_get
   and http_setauth(HTTP_AUTH_BASIC: userid : passwd) procedures.
   I have basic webservice, so I used the basic one. Since I don't have
   any web form for authentication like UPS, the alternative solution
   that you gave won't apply to me.
   But I am getting the http://1.1 internal server error.
   In your example you used http_url_get, with the second parameter as a
   web form('/testauth.html'), but I don't have any web page, I just have
   a url for webservice which doesn't open in browser.
   Can you please tell me what I need to do. How can I use your example?
   Your help is appreciable.
   >Message: 2
   >Date: Fri, 28 Jul 2006 17:32:12 -0500 (CDT)
   > From: Scott Klement <sk@xxxxxxxxxxxxxxxx>
   >Subject: Re: HTTPAPI : Only the http protocol is available!
   >To: HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
   >Message-ID: <20060728171906.E10942@xxxxxxxxxxxxxxxxx>
   >Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
   >Hi John,
   >When you reply to a digest, please change the message subject.
   >when people receive your mail, they just get a message with a subject
   >says "HTTP digest #123  . . ." and that's not very helpful.
   >this subject ends up in the archives, where it's not useful to
   >trying to solve the same problem.  So please just change it to the
   >subject of the message you're replying to, or else something like
   >"Userid/Password help".  Thanks.
   >EXAMPLE7 demonstrates how to set userid/password when a Web site uses
   >HTTP authentication mechanism (either basic or digest) to request a
   >and password.
   >I hope that the stuff in EXAMPLE7 solves the problem, because it's
   >simpler than the alternative -- I'll describe the alternative below:
   >Many sites don't use this mechanism. Instead, they'll present a web
   >where the user has to key in a userid/password.  This form works just
   >any other web form (such as those used for keying a search string
   >google, keying a ship-to address into Amazon.com, etc, etc) and isn't
   >specific to userid/password fields.  Usually after signing you in,
   >set a cookie with a session key so that they'll recognize you in the
   >To deal with that scenario you need to:
   >a) Turn cookies on before calling other routines in HTTPAPI
   >        http_use_cookies(*ON);
   >b) Look at the HTML code for the site to see what the form looks
   >There'll be <input> tags that describe the parameter name & data that
   >sent back to the server.
   >c) Create URL encoded parameters using the HTTP_url_encoder_xxxx()
   >routines from HTTPAPI. (Example2 demonstrates this... the parameters
   >set will be the ones you discovered in step b).
   >Once you've signed in this way, and the cookie has been set, you can
   >proceed to do whatever steps are next.
   >Scott Klement  http://www.scottklement.com
   >On Fri, 28 Jul 2006, John J wrote:
   > > Hi Scott,Thanks for your reply, the person who had installed
   > > didn't say Yes for HTTPAPI with ssl support. Now I reinstalled and
   > > time I am not getting that error, but I am getting error saying
   > > "This page requires a user-id & password". I think I am not
   > > user-id and password in right format. I tried the way that you did
   > > UPS tracking example and also https://<user>:<password>@url, but
   > > it's not working. Can you please let me know how can I do that,
   > > help is really appreciable.
   > >
   > > Thanks,
   > > John
   >This is the FTPAPI mailing list digest.  To unsubscribe, go to:
   >End of Ftpapi Digest, Vol 1, Issue 13


   1. http://adworks.rediff.com/cgi-bin/AdWorks/sigclick.cgi/www.rediff.com/signature-home.htm/1507191490@Middle5?PARTNER=3
This is the FTPAPI mailing list.  To unsubscribe, please go to: