Skip to content
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

OpenAPI traps exceptions, spewing them to the User without a logentry #126

Closed
stephan48 opened this issue Nov 13, 2020 · 0 comments
Closed

Comments

@stephan48
Copy link

This led me to chase a misnamed filter for a short time, as there was no apparent error on the mojo side, just inside the returned JSON upon saving/creating an entry.

Example:
2020_11_13_19_33_28_Yancy

And no log output.

-- stephan

preaction added a commit that referenced this issue Nov 15, 2020
This adds a `log_die` helper which can be used to make sure a log is
generated in a helper when an exception might be captured.

Thanks @stephan48 for reporting this issue!

Fixes #126
preaction added a commit that referenced this issue Nov 16, 2020
    [Fixed]

    - Prevent authentication return URL from redirecting somewhere
      offsite, which is a potential security risk:
      http://cwe.mitre.org/data/definitions/601.html
    - Fixed missing logs when an exception is caught. Thanks @stephan48
      for reporting this! [Github #126]
    - Fixed editor not displaying Internal Server Errors. It now
      displays an alert box with a button to show more details. Thanks
      @stephan48 for reporting this issue! [Github #127]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant