Discuss and finalize HTTP Header passing behaviour about ballerina-lang HOT 3 CLOSED

Incoming messages are targeted to a resource. A resource corresponds to an API (here I use the notion that each function offered is an API; sometimes the collection of offered functions is referred to as an API - not sure which notion we use). And an API specifies which headers are supported, both, inbound and outbound (refer to Swagger). Thus, each resource specifies the inbound headers it understands and which headers will be set in the response.

We have data mapping functions that allow to access (incoming) headers and set headers. Both is selectively, i.e. the data map used to create the message send to a backend is in charge of setting the headers of the message.

In that sense, the headers must be available within the Balerina logic but should not be "made available to the backend" by default.

from ballerina-lang.

@isudana can we resolve this?

from ballerina-lang.

The current implementation adheres to the HTTP spec with regards to which headers to forward and which headers to remove. Hence closing this.

from ballerina-lang.