We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
respondHtml
When using respondHtml, and a required param is not provided, something nasty happens to the nginx proxy on a production NixOS server.
Example:
action SomeAction = let someParam = param @Text "someParam" respondHtml [hsx|{someParam}|]
And then call http://siteUrl/SomeAction directly without the required parameter.
http://siteUrl/SomeAction
I get an nginx 502 Bad Gateway response which also takes the whole proxy down until systemd automatically restarts it.
502 Bad Gateway
systemd
It leads to a couple of seconds of downtime, making it possible for any user to bring the server down.
I would expect the error to be properly catched with an IHP error, as it seems to be with the render function (I think?).
render
The workaround would of course be to use paramOrNothing, although a bit inconvenient to remember.
paramOrNothing
Some additional info provided on this issue: #1837
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using
respondHtml
, and a required param is not provided, something nasty happens to the nginx proxy on a production NixOS server.Example:
And then call
http://siteUrl/SomeAction
directly without the required parameter.I get an nginx
502 Bad Gateway
response which also takes the whole proxy down untilsystemd
automatically restarts it.It leads to a couple of seconds of downtime, making it possible for any user to bring the server down.
I would expect the error to be properly catched with an IHP error, as it seems to be with the
render
function (I think?).The workaround would of course be to use
paramOrNothing
, although a bit inconvenient to remember.Some additional info provided on this issue: #1837
The text was updated successfully, but these errors were encountered: