Imagery offset server moved? ("JOSM: HTTP Response code 301 (Moved Permanently)")

Andrew_Chadwick · 2024-06-25T16:14:37.148Z

I’m using Debian’s JOSM 19096 with an old setup. Anyone else seeing 301 responses today when trying to get or store imagery offsets (e.g. Imagery → Get Imagery Offset…)?

Guessing there’s an infrastructure change afoot, and JOSM doesn’t seem to be able to handle the 301. If I knew what to change I would, but it’s not obvious which setting to prod.

TrickyFoxy · 2024-06-28T12:39:51.372Z

In the Advanced Preferences of JOSM (check Expert Mode), find the iodb.server.url and change http to https

SCR-20240628-nybv2104×1544 299 KB

Zverik · 2024-07-02T06:22:55.826Z

Hi guys, and sorry for that. I’ve enabled http back on the server, so no adjustments neccessary.

JassKurn · 2024-07-01T23:39:01.699Z

Been annoying me for days, and expecting it to fix itself. Nothing on the wiki page

Thankyou, TrickyFoxy for the solution.

I’m going to add a quick and ugly link to this post in wiki page. I’m going away for a couple of days and havent got time for proper editing.