March 1, 200619 yr I am trying to access secure environmental variables on a remote server by using the document() function. Does that make sense? I am working with 2 servers. One of the servers authenticates users by certificate. If a user has a certificate and they access a page on the server with https, then a script can access certain variables for that user. I have a perl script that can create some xml for a user. The other server holds the filemaker documents. I want to put a XSL document on this server that has the following code: For some reason this won't work, even though it says it will in the CWP guide. I get the following error: [color:green]The resource https://domain.edu/cgi-bin/rewards/certParams.cgi could not be loaded because of an unexpected error (MCS-604) Anyone have any ideas? Thanks, Moses Edited March 2, 200619 yr by Guest
March 1, 200619 yr When you load that link in a browser, you get an error message ... BTW: The returned content must be in XML
March 2, 200619 yr Author Thanks for your reply. I definitely have valid xml coming out. I tested the xml by putting it in a separate, non-secure xml document and it loaded just fine with document(). When I try the https file, which is a cgi, I get the error message [color:green]The resource could not be loaded because of an unexpected error If I take the 's' off of https then the error goes away.
March 2, 200619 yr Ah, I see. Of course you have (e.g. the browser) has a certificate, but the server not, because the document() function is executed server-side. That might result in the error because the .edu server first sends the certificate request, and document() does not know what to do with it. Could a possible solution be to install a standard certificate on the .edu server?
March 6, 200619 yr Author I see what you mean. Putting a certificate on the server is not a solution because each user has their own individual and unique certificate. Perhaps there is no solution. Thanks for your help, Moses Edited March 6, 200619 yr by Guest
Create an account or sign in to comment