Response step Content-Type feature request not implemented as intended

Wappler General Bugs
1

Wappler v7.3.6

Response step Content-Type feature request not implemented as intended

image
image696×508 15.5 KB

{
  "name": "",
  "module": "core",
  "action": "response",
  "options": {
    "status": 200,
    "data": "Hello"
  },
  "outputType": "text"
}

Content-Type is not set to text/plain, as feature request:

2

The data type here is only to indicate if you want a single string or a nested data object in the json response.

Server connect actions always return response type json

3

Then please re-open the feature request that was closed by Teodor, as Content-Type selection wasn't implemented as the feature request intends

4

@George @Teodor please re-open the feature request thread, as the feature was not implemented as the feature request specified. The intended use is not for use within AppConnect, as I mentioned it's for e.g. webhooks or other forms of external API interaction that don't follow Wappler conventions of all Server Actions return JSON.

Patrick's original solution:
Server Connect Response - forcing blank body - #22 by patrick?

1 Like