Cannot Login to QRZ.com

[VE1LG]

I am trying out RUMlogNG, version 5.19.4 (684) from the App Store, and everything is working nicely except lookups via QRZ.com. I have the correct username and password (I have checked, re-check, triple-checked etc) in the settings but lookups give me the following:

Error 3 parsing qrz.com:
Username/password incorrect

I get the same error if I just click the little triangle that opens up the lookup with. Or if I tab to a different lookup provider and then back to the QRZ.com tab.

My QRZ.com XML subscription is current and I've tested my login in other apps such as MacLoggerDX which works fine.

I am running RUMlogNG on an Intel Mac running Sonoma 14.7.6.

73,
Doug VE1LG

[VE1LG]

So I used mitmproxy to capture and view the https packets to/from xmldata.qrz.com with both MacLoggerDX (working) and RUMlogNG (not working).

MacLoggerDX uses

?username=the-callsign-here;passwd=the-password-here;agent=the-agent-here

Also, in my specific password I have special characters. MacLoggerDX escapes them all.


RUMlogNG uses

?username=the-callsign-here&password=the-password-here&agent=the-agent-here

RUMlogNG escapes most of the special characters in my password except for ; and :

I doubt the use of & vice ; to delineate GET parameters matters, but not escaping the semi-colon and colon in my password certainly does.

I will change my password to not have a semi-colon and colon and report back here.

[VE1LG]

Yup, can confirm. Replaced the semi-colon and colon in my password with alpha characters on qrz.com, then made that change in RUMlogNG as well and it is now working.

[DL2RUM]

Thanks for the hint Doug.
In fact, RUMlog fights with this problem since the beginning. I have to dive in it in again.

[VE1LG]

Ironically I had the same issue with my own Android app for QRZ lookups. So this should have been the first thing I looked at but it slipped my mind.

[DL2RUM]

It seems to be a common problem due to different interpretations of the standard. Apple writes here: https://developer.apple.com/documentati ... guage=objc

RFC 3986 specifies which characters must be percent-encoded in the query component of a URL, but not how those characters should be interpreted. The use of delimited key-value pairs is a common convention, but isn’t standardized by a specification. Therefore, you may encounter interoperability problems with other implementations that follow this convention.

[VE1LG]

It would be nice if standards were written such that they did not need interpreting. But a perfect world does not exist