Ticket Created
over 3 years ago

WERETECH-11951

Feature-request: allow makeWebRequest with "Content-Type"= text/html

I think Connect doesn't check the content of response only the header and if it is different than Communications.HttpResponseContentType it does not transmit data to the watch.

This limitation is unnecessary because I can prepare server to response in plain text/json and return html.

This limitation only adds extra work and expense in writing the server / proxy.

HTTP traffic shows:

Content-Type: text/html; charset=utf-8\r\n

and error is -400 and data null.

I don't expect help from API (like in REQUEST_CONTENT_TYPE_JSON, when API convert data to dictionary) only return data in string.