In the message summary, the HTML is not preprocessed for inline content, so if that HTML is rendered by the webapp, the inline content will not display.
Expected Behavior
When you query GET /rest/messages/ID/html, the HTML returned is preprocessed so that all CID:tokens are replaced with /rest/messages/ID/content/, so that clients can fetch the inline content for display.
However, the HTML returned in the messageBodyHTML is not preprocessed, and therefore contains the original CID: tokens. This is useless to any client trying to render that HTML.
barryoneill
commented
6 years ago
Question/Issue Overview
In the message summary, the HTML is not preprocessed for inline content, so if that HTML is rendered by the webapp, the inline content will not display.
Expected Behavior
When you query
GET /rest/messages/ID/html, the HTML returned is preprocessed so that allCID:tokens are replaced with/rest/messages/ID/content/, so that clients can fetch the inline content for display.However, the HTML returned in the messageBodyHTML is not preprocessed, and therefore contains the original
CID:tokens. This is useless to any client trying to render that HTML.