I am looking to authenticate a login session to a RETS server using Cold Fusion MX 6.1 and 7 (it should work in both). I do not anticipate this being longer than one template. In fact, I have already coded the page that works as follows: Step 1) intitial request to server, which provokes a 401 code response, allowing me to save the required login information to arrays (the server has particualr information it kicks back wih a 401 Unauthorized response that I must format and kick back in a second request). Step 2 is saving all of the required information and formatting it for a second request. I have this done but it is not formatted correctly because Step 3 fails. Step 3 is the second request....the response is supposed to be a 200 code, but I am receiving back a 401 or 'Bad Request' dependant upon the format I configure. I have been trying this with cfhttp, but do not care how it is done as long as 1) nothing needs to be loaded by the cold fusion administrator (I am using a shared hosting cold fusion program for this so I do not have access and dont wish to try) and 2) the authentication starts a session that allows me to then send queries (which I will code myself using protocol). and 3) this needs to be written in coldfusion. In effect for someone who is familiar with HTTP 1.0 authentication, or particularly RETS authentication this can be handled in a hour using the code I will provide and reformatting it.
My trial page is at this link, [url removed, login to view]
You wil see the initial response ([url removed, login to view]) then the arrays and structures holding the response material, then the second response below. I have attached the code that generates the page on the link below. All interaction documentation for the RETS server can be found at [url removed, login to view] under the documents link. I a m looking at version 1.5 at this link [url removed, login to view] ...check out the login section.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Cold Fusion MX 6.1 AND 7 as a web page