[Rets-dev] search problems on rapattoni server

[Tony Manhollan]

Hi Joe,

You might try ListingPrice instead of SearchPrice. I¹m not sure about that,
but I seem to recall doing a query like that against one of the Rapattoni
servers a while ago when I first started working with it. I think I
encountered a similar problem. If you haven¹t already, you might want to
read Rapattoni¹s release notes on its server[1] as there are other query
requirements and download limits set out in it. There is a requirement that
all queries contain some combination of fields in the search clause.
MLNumber is one requirement, so the price query might be something like
((MLNumber=0+),(ListingPrice=150000+)), which should give you any listing
with an asking price over $150,000 (and an MLNumber greater than
0<effectively any listing). That is, of course, if ListingPrice doesn¹t have
the same restriction placed on it as SearchPrice.

If that doesn't work, I'd try Rapattoni support again. I agree with Keith
that the error you gave is not likely caused by the requirement in section
4.10. I don't think it's the cookie issue either. I'm using librets and I
don't have any communication or authorization problems with either of the
Rapattoni servers I connect to. Librets does handle all that communication
stuff transparently. Perhaps if you sent an http trace to Rapattoni's
support showing your request and the server's response, they might be able
to tell you if there are in fact any technical problems with the request or
if it's something with the query.

Good luck.

Tony Manhollan
Realestatepointe.com

[1] Rapattoni's RETS 1.5 server Release Notes
http://www.rapattoni.com/supp/mls/rets/documents/PDF/RETS1_5_Product_Release
_Notice.pdf


> From: "Keith T. Garner" <kgarner at crt.realtors.org>
> Date: Thu, 29 Mar 2007 19:23:11 -0500
> To: Joe Marino <joey.da3rd at gmail.com>
> Cc: rets dev mailing list <rets-dev at rets.org>
> Subject: Re: [Rets-dev] search problems on rapattoni server
> 
> Joe Marino wrote:
>> Hello all,
>> I am somewhat new to RETS and relatively new to software development. I
>> am building a custom client for a my customer (My Dad). It took me a
>> while and lots of help from Keith but I finally able to login!! I am
>> having a problem searching on a rapattoni server. I understand that
>> there are search requirements for this server in which I have access to
>> only limited search fields and only in conjunction with certain fields.
>> However, whenever I try to perform a legal search, I get an error saying
>> I do not have access to a certain field.
>> 
>>  `Search': Unauthorized query. The query could not be executed because
>> supplied login does not have access to the SearchPrice field.
>> (ArgumentError)
>> 
>> I've been reading through the documentation and I believe the problem
>> lies in my understanding of the RETS specification.  When I login and
>> request capability urls, I am given a search but not an action URL. In
>> section 4.10 of RETS 1.7 it states: "A URL (action-url) on which the
>> client MUST perform a GET immediately after login.... A server is not
>> required to supply an action URL."  My client does not perform a GET
>> after logging in because I am not supplied one. Is this something I need
>> to worry about?
> 
> This should not be causing a problem, at least not the one you have listed
> above.  However, you can call RetsSession::GetAction() to be sure.
> 
>> I also noticed the search URL is different than the login URL, which
>> makes sense, but am I going to have to somehow change the session (using
>> librets btw) over to this search URL before querying the server in order
>> to perform a search?
> 
> librets handles that for you transparently.
> 
>> When I called Rapattoni RETS support for assistance, because I believed
>> I wasn't given the necessary permissions, he mentioned something about a
>> cookie that I am not receiving. Am I to request this cookie separate
>> from the login transaction?
> 
> librets handles that for you transparently.  libRETS will send back all
> cookies that the server sends it.  You can use HTTP logging or perform a
> packet trace something like wireshark or ethereal to confirm
> 
> You may also want to try settings RetsSession::UseHttpGet(false).  Due to
> confusion in how the DIGEST-AUTH has been implemented, sometimes this fixes
> authentication/authorization issues.  ezRETS (which is built on libRETS)
> defaults to this behavior and rarely has issues.
> 
> Keith
> 
> -- 
>   Keith T. Garner - Managing Director - Center for REALTOR® Technology
>    kgarner at realtors.org - 312-329-3294 - http://blog.realtors.org/crt
> 
> _______________________________________________
> Rets-dev mailing list
> Rets-dev at rets.org
> http://lists.rets.org/mailman/listinfo/rets-dev



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rets.org/pipermail/rets-dev/attachments/20070330/95eccb56/attachment.html