SAC Web application enabled for hospital staff.
Users successfully login to SAC Portal and launch application via browser.
Users can browse set of images (x-rays) and once an image is selected, a callback arrives from the back end web server that auto launches an thick application, which is an image viewer applications.
When this application launches, instead of rendering the expected image, it returns the following error message :
"The content type text/html of the response message does not match the content type of the binding (multipart/related;type="application/xop+xml"). if using custom encoder, be sure that IsContentTypeSupported method is implemented properly."
SAC Web Application.
Thick Applications to view images on back end Web site.
No session information inherited by image application when sending request into SAC.
With this use case, there are two possibilities:
1. Enable session sharing between the various user-agents used within this solution (browser and image viewing application): This can be done by extending the application to include browser style code that can handle redirects and authenticate users. The current version of the Application could not handle redirects and was hard coded to view images.
2. Instead of using a Web application, use a TCP application instead.
App callback fails to render data due to missing session info.
No session sharing between the two User-agents (browser and thick Application)
HAR/Fiddler file will not show much as control is passed from browser to the image application that does not log anything.
Application error message indicates that the content-type is unexpected because they are not getting the expected image with corresponding content-type, but the SAC login page which uses text/html.