-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http endpoint does not return error and continues #256
Labels
Comments
Not a Beelzebug :-) The service http://showcase.api.linx.twenty57.net/UnixTime/tounix?date=now is often offline, I will update the example with an endpoint that is more stable |
The bug is on error signaling to reproduce, old example:
KEYS:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Run the
Http: read the output of an endpoint
example on apiroom.netExpected 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
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
The text was updated successfully, but these errors were encountered: