Kein Upload Ver 1607/1632 | Uploading fails stating "Cannot read numeric value from response"

[anonymous]

Der Upload schlägt fehl mit der Meldung:"kann keinen numerischen Wert aus der Antwort lesen"
Fehler tritt beim Öffnen des Änderungssatzes auf.

[oliver@…]

screenshot

[augustus.kling@…]

Dies trifft auch auf die Version 1632 zu.

This also applies to version 1632. It fails stating "Cannot read numeric value from response" before asking for a users password. Output in the operating system's console is (with my plugins):
loading plastic_laf
loading measurement
loading validator
loading wmsplugin
Open file: [path to local file] (2067414 bytes)
GET ​http://www.openstreetmap.org/api/capabilities... OK
Communications with ​http://www.openstreetmap.org/api established using protocol version 0.6
PUT ​http://www.openstreetmap.org/api/0.6/changeset/create... OK

Although I tried to upload data from an existing file, I can confirm that the error also appears after only downloading and manipulating data.

[augustus.kling@…]

I'm still wondering why the console output tells me that the changeset/create request finished with status OK although I wasn't asked for my credentials yet. The server denies requests by telling "Couldn't authenticate you".

[indigoboy]

I can confirm this bug. No upload possible for me at the moment.

[anonymous]

I checked this again and it worked for me now. I did use the same JOSM version as when I experienced the bug as mentioned above.
The changed behavior of the OSM API was the source of the issue. Now, it is requesting a user's name and password again which seems to make JOSM show the password dialog. As a result uploads are working again without problems.

Although this is working again I think this ticket is still valid as JOSM's message is not understandable for users that aren't familiar with the OSM API. Due to this reason the message should be changed.
Additionally the console output "​http://www.openstreetmap.org/api/0.6/changeset/create... OK" should be changed since the server's response was not okay. What about printing out the server's response body into the console and maybe an error message box if the response failed?

Essential translation for German users:
Das Hochladen von Änderungen funktioniert nun wieder (auch mit den selben Versionen von JOSM). Ursache des zeitweiligen Problems war ein geändertes Verhalten auf Seite des OSM-Servers.

[stoecker]

An better josm message requires an common problem, so messages can be adapted. Closing this. New bugs may be opened for more generic message problems.