Skip to content

Http effect: no custom headers support #351

@aallan

Description

@aallan

The Http effect (#57) MVP provides get and post operations that send requests with default headers only. There is no way to set custom request headers (e.g. Authorization, Content-Type, Accept) or read response headers.

Impact

APIs requiring authentication tokens, custom content types, or API keys in headers cannot be used from Vera.

Possible fix

Add an HttpRequest ADT with headers as Map<String, String>, or add header-aware variants:

op get_with_headers(String, Map<String, String> -> Result<String, String>);

Related: #57 (Http effect), #305 (HTTP Server)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestlimitationKnown compilation limitation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions