Skip to content

http endpoint does not return error and continues #256

Description

@jaromil

Steps to reproduce

Run the Http: read the output of an endpoint example on apiroom.net

Expected behavior

The HTTP endpoint for getting a timestamp is some random and obscure site that doesn't works anymore:
"timeServer": "http://showcase.api.linx.twenty57.net/UnixTime/tounix?date=now"

Instead of returning an error, restroom goes on using the error string instead of the timestamp

   "timestamp-output": {
      "status": "ENOTFOUND"
   }

This is very dangerous in use-cases explained by this example, where a timestamp is used to enhance the random generation, but instead it will damage its entropy by using a constant error string.

Actual behavior

Restroom should block execution and return an error when an HTTP endpoint is not reachable, indicating clearly the endpoint and its error status and code. I suspect this should be the behavior also in case of database connections failing or DB objects not found: the zencode developer should know that the string returned is a constant error.

System configuration

Latest Apiroom deployment on 22 June 2023

  • Release version: v3.5.1
  • Build commit hash: 88acb427

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions