Reply To: Using HTTP-Client Protocol

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Using HTTP-Client Protocol Reply To: Using HTTP-Client Protocol

#58096
Ed Mastascusa
Participant

    To attempt to answer your questions:

    >> Am not sure what is the server side script you are talking about.  

    The one in the error message (marked below)

    Error fetching URL http://development.intranet/temp/cloverleaf/default.aspx: <-- here HTTP/1.1 500 Internal Server Error >> Is it a WebServer Side Script?    

    I think so

    >> Could you please explain about the script clearly?

    If your URL has a suffix of .pl, .php, .asp or something other than .xml or .htm(l) then the web server is probably running a script on the server to create the response.

    My experience (Apache on Linux using perl/tcl) is that you’ll see a “500” error returned to the client when the http request gets to the server and activiates the script but for some reason the script fails to produce valid output. I can recall achieving(?) 500 errors from a number of mistakes, the most common being that my scripts had syntax or logic problems that caused them to croak while making the response. Either the header (which someone mentioned earlier) was missing or made wrong or was missing altogether. Another cause could be that the script permissions weren’t set to allow the web server to launch the script.  Another common error would be a 404 – file not found – which could happen if the URL referenced a non-existent script. Since you see a 500 it says to me that the request got to the server and was acted upon, but that for some reason a properly http reply did not come back to the client.

    >> How do we post via some other method and get a valid reply?

    Your method can generally be “get” or “post”. more detail can be found here:  http://www.cs.tut.fi/~jkorpela/forms/methods.html

    A browser is just an HTTP client to the web server, although most URLs are implicitly using a get in the browser and you had mentioned using post.  It probably can’t hurt to just surf to  “http://development.intranet/temp/cloverleaf/default.aspx” in your browser and observe what happens. If you see an error 500 in your browser then your problem is not likely in the client