Don't re-write fcr:fixity links #1996
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA Ticket: https://fedora-repository.atlassian.net/browse/FCREPO-3831
What does this Pull Request do?
Currently when you upload a binary you get a
fedora:hasFixityServicetriple, it is getting redirected tohttp://localhost:8080/rest/<uri>/fcr:fixity/fcr:metadata. This should not be redirected.How should this be tested?
Before the PR add a binary and click the
fedora:hasFixityServicelink in the HTML UI. Get an 404 white page in the browser.Pull in the PR and try again, get the fixity result.
Interested parties
Tag (@ mention) interested parties or, if unsure, @fcrepo/committers