using rets-version=rets/1.8 I am getting response unauthorized
Earlier I am using the 1.7.2 version of RETS now I am using the 1.8 so credentials will same or not for the upgraded version? new version of RETS i am getting unauthorized
Authentication is the same for RETS/1.7.2 and RETS/1.8.
What RETS URL and login account name are you using (NO PASSWORDS)?
Were you able to get this working?
We are still getting the unauthorized RETS URL- http://yuma.rets.paragonrels.com/rets... accountname - genreal
I am seeing requests from RETS Connector for your account as recent as today?
Are you still not working?
. I was able to connect using your account using RETS/1.7.2 and RETS/1.8
how can you are able to connect with using RETS/1.8? I am still not able to connect with RETS 1.8. I am using the below parameter. "UserAgent": "RETS-Connector/1.8", "ServerVersion": "1.8", "LoginUrl": "http://yuma.rets.paragonrels.com/rets/fnisrets.aspx/YUMA/login?rets-version=rets/1.8" Today we have used the RETS 1.7.2 and 1.8 both when we are using the 1.7.2 at that we are able to fetch the data. If I am missing something for 1.8 Please let me know.
Are you using RETS Connector to connect to RETS or are you just using that as your User-Agent?
The only change needed is to set the rets-version=RETS/1.8 which can be set in the RETS connector server options.
If you aren't using RETS Connector, you can add the header: RETS-Version=RETS/1.8 in each of your requests or you can pass it as the URL parameter like shown on your login URL above.
You don't need to change the User-Agent or the ServerVersion.
Now I am able to connect with RETS 1.8 as per your suggestion dont need to change User-Agent or the ServerVersion. But here I am facing issue while fetching the data after some time I am disconnecting automatically.
Sometimes pulling metadata can be a little slow. Make sure to set your connection timeout to a longer value.
currently we didn't have gives any timeout value where we need to add the time out value? what is the parameter name? Can I use Timeout : {time_in_seconds}
Any Update?
Are you still having issues with this?
Yes I am still facing that issue!