RUMlog 5.2.6 and qrz xml subscriber

[kf5jra]

Just recently switched to RUMlog from another Mac based logging program to get a better handle on tracking my QSL's. Everything has went well with the log import and now have a better idea of what I need for my first WAS. I have also had great success in logging both phone and psk31 contacts.

I have a qrz XML subscription and have put my qrz credentials in for qrz but I receive no data on my lookups. I have a hamqth account also setup and at the moment I am relying on that till I can figure out the issue with RUMlog and my xml access. I have also loaded RUMlog2go on my iPhone and linked it my log stored in Dropbox and this is working perfectly for logging contacts while mobile and being able to lookup calls with my qrz xml subscription.

I ran a tcpdump on my local network to see why RUMlog2go works on a qrz lookup but not in RUMlog. The packet traces revealed that RUMlog2go is using the xmldata URL (http://xmldata.qrz.com/xml?s=) and that RUMlog is using the browser URL (http://qrz.com/lookup). Is this URL compiled into the binary of RUMlog or is it stored in a .plist file. Reason for the last question is that before swathing fully to RUMlog I have been keeping a version on my system for testing since version 5.x

Any ideas what could be the issue. I am currently using HamQTH for lookups till I can get this resolved but would really like to use what I have paid for.

TIA
-Ron

[DL2RUM]

I have a qrz XML subscription and have put my qrz credentials in for qrz but I receive no data on my lookups.

Do you get an error message or just nothing?


The Mac version is using the same qrz address: http://xmldata.qrz.com/xml
I can't find and links to http://qrz.com/lookup in the source. So I'm a little bit helpless.

[kf5jra]

I get "No Data" in the pull out drawers of RUMlog and no population of any of the fields "Name", "Location", etc

So there is no .plist file that could be holding an old setting somewhere.

Thank you for replying so quickly

[DL2RUM]

You put a call sign into the call sign field and you go to Menu-->QSO-->qrz.com Look up

This returns "No data"?

[kf5jra]

You put a call sign into the call sign field and you go to Menu-->QSO-->qrz.com Look up

This returns "No data"?

Here is a link to a screenshot of what I get when I do a lookup.

https://dl.dropboxusercontent.com/u/359338/qrz-ss.tiff

Notice the lack of data in the drawer and in the main logging window.

[DL2RUM]

Are you sure, you are clicking: Menu-->QSO-->qrz.com Look up ??? I'm wondering since you have got qsl information.

[kf5jra]

Are you sure, you are clicking: Menu-->QSO-->qrz.com Look up ??? I'm wondering since you have got qsl information.

Yes and here is the GET Request: "GET http://www.qrz.com/qsl/?callsign=DL2RUM" from my tcpdump. I have even verified that my RumlogOwn.plist file has the correct credentials for qrz written to it as well. Notice that the URL is not xmldata.qrz.com

[DL2RUM]

"GET http://www.qrz.com/qsl/?callsign=DL2RUM" from my tcpdump

This is very helpful and indicates that you have selected: Menu-->QSL-->qrz.com QSL Lookup
Please try Menu-->QSO-->qrz.com Lookup

[kf5jra]

"GET http://www.qrz.com/qsl/?callsign=DL2RUM" from my tcpdump

This is very helpful and indicates that you have selected: Menu-->QSL-->qrz.com QSL Lookup
Please try Menu-->QSO-->qrz.com Lookup

Thom,

I have figured out the issue and have found a work around. My network has a web proxy between my network and the Internet. From what I can tell it is not liking the "User-Agent" string that you use for the RUMlog Mac app (agent=RUMlog 5.2.6 by DL2RUM) when requesting from xmldata.qrz.com. The "User-Agent" string you use for the IOS app is (agent=RUMlogToGo) which my proxy has no issue with. The work around for this issue was to put in a bypass for xmldata.qrz.com so it no longer goes through the proxy. Once this was done it now works. Possible solution for the Mac.app is to place the agent string in quotes for the web request.

Thank you for your time and assistance in assisting me with tracking this down. The confusing part was that it works on the IOS app but not the Mac app till i put in the bypass.