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.

Sign up for GitHub

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

Jump to bottom

HTTP 404 instead of empty response if not found #1580

Merged

Keats merged 1 commit into getzola:next from vilcans:next

Aug 6, 2021

Contributor

vilcans commented Aug 6, 2021

Fixes #1578

Problem was that if tokio::fs::metadata (which gets data about the file) failed, zola didn't return a proper HTTP error code.

Sanity check:

Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Code changes

(Delete or ignore this section for documentation changes)

Are you doing the PR on the next branch?

If the change is a new feature or adding to/changing an existing one:

Have you created/updated the relevant documentation page(s)?


          HTTP 404 instead of empty response if not found

691f4e3

Fixes getzola#1578

Keats merged commit 040b0de into getzola:next

Collaborator

Keats commented Aug 6, 2021

Thanks!

Keats pushed a commit that referenced this pull request


          HTTP 404 instead of empty response if not found (#1580)

17f3fe2

Fixes #1578

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet