Switch HamQTH API URL to HTTPS

[aa5sh]

Updated the API_URL in HamQTH.h to use HTTPS instead of HTTP for secure communication with the HamQTH service. It was failing without https. Reported by ZB3Z

[foldynl]

thanks...I don't understand that...I'm careful about using https and here it's http all the time.

[aa5sh]

With me it would just fail on my testing. He would get an error. I saw on their website the had http for legacy access so not sure if they turned it off or anything.

…

On Sun, Jan 11, 2026 at 10:05 AM Ladislav ***@***.***> wrote: *foldynl* left a comment (foldynl/QLog#886) <#886 (comment)> thanks...I don't understand that...I'm careful about using https and here it's http all the time. — Reply to this email directly, view it on GitHub <#886 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXQA4HC3WOKV5E66QPD4GJYFLAVCNFSM6AAAAACRKVYOCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZUHA4TONRYGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[foldynl]

so does that mean the fix should be released quickly? I am planning to include it in v0.48 within 3 weeks. Do you think it should be released in 0.47.2? I ask because HamQTH works for me without the change.

0.48 doesn't have such a change in the code, but there is a change in QT for Windows and Flatpak + a big change for Omnirig. So I test it a lot and unfortunately I find bugs somewhere else. So that's why 0.48 is a little bit delayed.

[aa5sh]

I would think it can wait. It doesn’t make sense why it would work in same instances and not others. I poked around a little with 0.48Dev. I was going to try your Windows build script this evening. I had been working on one similar, and have one for MacOs. I can clean up my Mac one and share it with you if you want so it would be available for others. Main thing I need to do is remove my signing credentials and make it where it would be self signed to make MacOS happy.

…

On Jan 12, 2026, at 9:03 AM, Ladislav ***@***.***> wrote: foldynl left a comment (foldynl/QLog#886) <#886 (comment)> so does that mean the fix should be released quickly? I am planning to include it in v0.48 within 3 weeks. Do you think it should be released in 0.47.2? I ask because HamQTH works for me without the change. 0.48 doesn't have such a change in the code, but there is a change in QT for Windows and Flatpak + a big change for Omnirig. So I test it a lot and unfortunately I find bugs somewhere else. So that's why 0.48 is a little bit delayed. — Reply to this email directly, view it on GitHub <#886 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXWLRVA23K6UYLQQP3D4GOZTRAVCNFSM6AAAAACRKVYOCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZZGAYDENJZGE>. You are receiving this because you authored the thread.

[foldynl]

This may be a different thread, but yes, I prepared automated scripts for Windows, because the release procedure today takes 1 hour, which is a lot of time and a lot of manual work, especially on Windows. That's why it was created. I appreciate your MacOS autobuild. I like that. Just a question, do you know if and how difficult it is to be a part of the homebrew cask?

[aa5sh]

I had looked into it months ago, but honestly don’t remember why I paused. I will look into it again. I think since the Mac builds were on my GitHub it wanted some history I think. I will read up on it again tonight and let you know.

…

On Jan 12, 2026, at 9:23 AM, Ladislav ***@***.***> wrote: foldynl left a comment (foldynl/QLog#886) <#886 (comment)> This may be a different thread, but yes, I prepared automated scripts for Windows, because the release procedure today takes 1 hour, which is a lot of time and a lot of manual work, especially on Windows. That's why it was created. I appreciate your MacOS autobuild. I like that. Just a question, do you know if and how difficult it is to be a part of the homebrew cask? — Reply to this email directly, view it on GitHub <#886 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXX5EXFLCRP2RASGNJ34GO36JAVCNFSM6AAAAACRKVYOCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMZZGEYTCMJUGA>. You are receiving this because you authored the thread.

[foldynl]

@aa5sh I have opened an issue #891 about the homebrew cask. It will be better to keep this in another thread.