Modify ↓

Opened 6 years ago

Closed 5 years ago

#130 closed enhancement (fixed)

"translate" osm server errors into human readable strings

Reported by: ulfl Owned by: imi
Priority: minor Component: Core
Version: latest Keywords:
Cc:

Description

Currently we have a lot of server problems, resulting in errors if you try to download osm data.

While a common josm user might know what a HTTP 404 message means (however, it's still hard to predict what to do then), a "Server returned HTTP response code: 500 for URL ..." gives you no idea about the problem and what to do now.

So it would be a good idea to "translate" these codes into something more human readable:

Internal Server Error - please try again later

Server returned HTTP response code: 500 for URL ...

Attachments (0)

Change History (2)

comment:1 Changed 5 years ago by anonymous

  • Priority changed from major to minor
  • Type changed from defect to enhancement

comment:2 Changed 5 years ago by anonymous

  • Resolution set to fixed
  • Status changed from new to closed

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed .
as The resolution will be set. Next status will be 'closed'.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.