Project

General

Profile

Actions

feature request #2711

open

Proper handling of cdm webservice HTTP status codes

Added by Andreas Kohlbecker about 12 years ago. Updated about 5 years ago.

Status:
New
Priority:
Priority09
Category:
cdm-dataportal
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
critical

Description

Currently the HTTP status codes returned by the cdm web-service are neglected. For example a call to http://160.45.63.151:8080/cichorieae/portal/taxon/37d81a19-8d8c-44e8-8140-a6d2aaab4149/synonymy causes an HTTP ERROR 500. The resulting json object returned by the cdm_ws_get() function is null but the user is not informed about the error that occurred. The synonymy page of Askellia benthamii ( http://wp6-cichorieae.e-taxonomy.eu/portal/?q=cdm_dataportal/taxon/37d81a19-8d8c-44e8-8140-a6d2aaab4149/synonymy ) is almost empty.

We need to find a way to handle these errors properly, that is to inform the user on such problems. But keep in mind that it might be necessary to ignore HTTP errors in some cases, that is to suppress warning messages.


related tickets which could have benefited from better http status handling.

consider to display notifications in the according web page part to notify the user that this part has problems.

  • #4972 (cyprus: mixed vocabularies break custom status colors)

Related issues

Blocks EDIT - feature request #7513: Proper user feedback on attempt to access unpublished taxonNewAndreas Kohlbecker

Actions
Actions #1

Updated by Andreas Kohlbecker about 12 years ago

  • Priority changed from Priority11 to Highest
  • Severity changed from major to critical
Actions #2

Updated by Andreas Kohlbecker almost 9 years ago

  • Target version changed from cdm_dataportal - Next Major Release to DataPortal - Reviewed Next Major Release
  • Priority changed from Highest to Priority13

see also [#4977#note-4]

in case of errors in the search web service the result says "No matching entries found". It should better say that an exception occurred if possible.

Actions #3

Updated by Andreas Kohlbecker almost 9 years ago

  • Priority changed from Priority13 to Priority12
Actions #4

Updated by Andreas Kohlbecker over 5 years ago

  • Description updated (diff)
  • Private changed from Yes to No
Actions #5

Updated by Andreas Kohlbecker over 5 years ago

Actions #6

Updated by Andreas Müller about 5 years ago

  • Priority changed from Priority12 to Priority09
Actions

Also available in: Atom PDF