fix prefix 500 status error

[wendelfabianchinsamy]

Purpose

closes: datacite/datacite#2109

Approach

Open Questions and Pre-Merge TODOs

Learning

Types of changes

• Bug fix (non-breaking change which fixes an issue)

• New feature (non-breaking change which adds functionality)

• Breaking change (fix or feature that would cause existing functionality to change)

Reviewer, please remember our guidelines:

• Be humble in the language and feedback you give, ask don't tell.
• Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
• Offer suggestions on how to improve code e.g. simplification or expanding clarity.
• Ensure you give reasons for the changes you are proposing.

[jrhoads]

Can you add a test for this potentially based on the original bug report?

[wendelfabianchinsamy]

Can you add a test for this potentially based on the original bug report?

We already have a bunch of specs testing the 404 scenario. The reason this bug exists is because this file was deleted from the repo during the Rails 7 upgrade.

[jrhoads]

Can you add a test for this potentially based on the original bug report?

We already have a bunch of specs testing the 404 scenario. The reason this bug exists is because this file was deleted from the repo during the Rails 7 upgrade.

Ahh. I see. It's a 500 error, not something that should happen in the course of the applications function, nor something we should be expecting (as tests do).