search

opencast / annotation-tool

A video annotation service that is suitable for research, teaching and learning
Educational Community License v2.0
40 stars 19 forks source link

Better error handling for misconfigured Opencast #86

Open JulianKniephoff opened 6 years ago

JulianKniephoff commented 6 years ago

When the API routes are not accessible due to missing or wrong settings in the Opencast confiuration, the frontend behaves unpredictably and is not very helpful. Sometimes it just hangs in the loading phase, sometimes it things the current user can't annotate the given video.

We can detect these scenarios somewhat cleanly: For example the /users endpoint never returns a 403 in normal operations (at the moment ...), but would do so if Opencast's security configuration doesn't let the request through. Also none of the endpoints used should ever return 405, which is returned when the impl bundle is not loaded properly.

We could display some kind of hint/error message in these cases.

mtneug commented 6 years ago

We noticed something similar after some users complained about "not saved data". In this case the Session expired (by default 5 min. in Opencast!) resulting in the unofficial HTTP error code 419. The solution was to prolong the session timeout by setting the org.ops4j.pax.web.session.timeout property in the org.ops4j.pax.web.cfg configuration file.