Fixes #23246 - branches/tags end with txt product invalid response
What does this MR do?
Fix the invalid API single branches/tags response if it ends with
Are there points in the code the reviewer needs to double check?
Should not. I only enforce the content type of those 2 APIs to
application/json, should not have any side effect to others.
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
- Changelog entry added, if necessary
- Documentation created/updated
- API support added
- Tests added for this feature/bug
- Conform by the code review guidelines
- Has been reviewed by a UX Designer
- Has been reviewed by a Frontend maintainer
- Has been reviewed by a Backend maintainer
- Has been reviewed by a Database specialist
- Conform by the merge request performance guides
- Conform by the style guides
- If you have multiple commits, please combine them into a few logically organized commits by squashing them
- Internationalization required/considered
End-to-end tests pass (
package-and-qamanual pipeline job)