Opened 15 years ago
Closed 15 years ago
#2619 closed defect (invalid)
JOSM displays an empty error message when the server returns "422 Unprocessable Entity"
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | uploading | Cc: |
Description
When trying to delete way 22529607 (.osm file attached) JOSM will create a changeset, send a osmChange request to delete the way, but shows an empty message dialog when the server returns "422 Unprocessable Entity".
The server is handling this case incorrectly, but JOSM should at least display the HTTP error message it gets.
Attachments (2)
Change History (5)
by , 15 years ago
Attachment: | 22529607-full.osm added |
---|
by , 15 years ago
tcpflow -c output of traffic between JOSM and the API when trying to delete the way
follow-up: 2 comment:1 by , 15 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
maybe this is the same as #3124.
Which JOSM did you use?
comment:2 by , 15 years ago
comment:3 by , 15 years ago
Resolution: | → invalid |
---|---|
Status: | needinfo → closed |
Can't reproduce anymore because the way 22529607
has been deleted in the meantime.
You've been working with [1605] according to the log you supplied. This is quite old. I'm pretty confident that recent releases always at least display the {{{toString()} text of an exception.
Closing as invalid.
22529607/full.osm