From @crwood: so there is way to have tahoe omit the HTML-ization of HTTP 500 error bodies (from the WAPI docs):
Unusual exceptions may result in a 500 Internal Server Error as a catch-all, with a default response body containing a Nevow-generated HTML-ized representation of the Python exception stack trace that caused the problem. CLI programs which want to copy the response body to stderr should provide an “Accept: text/plain” header to their requests to get a plain text stack trace instead.
We should ensure that magic-folder's tahoe-API usage includes the right header to get plain-text traces instead of HTML.
From @crwood: so there is way to have tahoe omit the HTML-ization of HTTP 500 error bodies (from the WAPI docs):
We should ensure that magic-folder's tahoe-API usage includes the right header to get plain-text traces instead of HTML.