Submit the history html 404 pushed by client

[ayanjoyful]

• Gitea version (or commit ref):
• Git version:1.7.6
• Operating system:
• Database (use [x]):
  • PostgreSQL
  • [*] MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • Not relevant
• Log gist:

Description

As shown in figure:
The commit history in the red circle is from the client,Click on the error.Page 500.
Background the log Error Page 404
...

Screenshots

[lunny]

Could you confirm that v1.8.0 fix that?

[saitho]

Did you click on the commit hash or did you click on the commit message (7777777777)?
If latter one: that is because Gitea sees that as a possible SHA hash and links it to a commit.

Example on try.gitea.org (latest commit): https://try.gitea.io/saitho/test/commits/branch/test2

[mrsdizzie]

For consistency we probably shouldn't render the commit Subject with the post processors so there aren't any autolink type things generated -- which means every Subject in that main list view will link to the actual commit without the chance that some link elsewhere.

Separate, this is probably another instance where if we checked if a hash existed first it wouldn't generate the link (though none of these subjects should end up links to elsewhere even if they are valid).

[lunny]

It seems this should be backport to release/v1.8