Bug #15606
closed
[keep-web] logging doesn't include error messages
Description
Community user on gitter is attempting to set up keep-web. It was first returning a 400 status code (which we determined could be worked around by setting TrustAllContent: true but there is no indication about why it was failing). After that it returned a 500 status code (still haven't figured it out). Keep-web needs to log error messages make it possible to diagnose failures.
Updated by Peter Amstutz over 5 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 5 years ago
- Description updated (diff)
- Status changed from In Progress to New
Updated by Tom Clegg over 5 years ago
- Target version changed from To Be Groomed to Arvados Future Sprints
Updated by Peter Amstutz over 5 years ago
- Related to Bug #15713: [Controller] Internal error not logged added
Updated by Peter Amstutz over 5 years ago
- Related to Bug #15521: [keepstore] error reporting improvements added
Updated by Tom Clegg over 5 years ago
- Assigned To set to Tom Clegg
- Target version changed from Arvados Future Sprints to 2019-11-06 Sprint
Updated by Tom Clegg over 5 years ago
Updated a few error messages, including the "400 can't serve inline content because XSS" error, which was sending no text at all, and was almost certainly the one that motivated this issue.
15606-keep-web-errors @ fb3568c55a9f64a6027fcfe78ca21a79461ea348 -- https://ci.curoverse.com/view/Developer/job/developer-run-tests/1614/
Updated by Lucas Di Pentima over 5 years ago
15606-keep-web-errors LGTM, thanks!
Updated by Tom Clegg over 5 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|e5a8dfa1ceeceacf8a51e99d2138d4b2b89411e8.