I found one MLS RETS implementations will raise an error if you pass RETS-UA-Authorization where there is a User-Agent but not a User-Agent-Password. Most MLS don't have an issue with it, so default should be to send RETS-UA-Authorization.
Additionally, this MLS also returns non-standard encoding in case of errors, but otherwise returns standard non-problematic encoding if the response is normal. Therefore, I added an exception in the case of non-standard response to parse it as raw binary, which is successful.
Details from RETS 1.7.2 specification regarding RETS-UA-Authorization:
I found one MLS RETS implementations will raise an error if you pass
RETS-UA-Authorizationwhere there is a User-Agent but not a User-Agent-Password. Most MLS don't have an issue with it, so default should be to send RETS-UA-Authorization.Additionally, this MLS also returns non-standard encoding in case of errors, but otherwise returns standard non-problematic encoding if the response is normal. Therefore, I added an exception in the case of non-standard response to parse it as raw binary, which is successful.
Details from RETS 1.7.2 specification regarding RETS-UA-Authorization:
testing passes: