[issue937] Error details from failed push hook not displayed to HTTP client

[Jesse Glick]

New submission from Jesse Glick <jesse.glick at sun.com>:

If a repository on a server has configured some pretxnchangegroup hook which
displays an error message when it fails (e.g. hgext.win32text.forbidcrlf), and
this repository is accessed over HTTPS from a client (via hgwebdir.cgi), the
client hg program does not display the failure message when the push is
rejected. It only gives the name of the failed hook.

This is a usability problem; the developer attempting to push might not have
been made aware of the details of what pre-push hooks are installed and may be
surprised by the rejection and not know how to correct it. For example,
hgext.win32text.forbidcrlf when run as a pre-push hook prints a rather detailed
message about what is wrong and how it could be prevented in your local
repository in the future, but all this is lost when serving over HTTP(S).

----------
messages: 4924
nosy: jglick
priority: bug
status: unread
title: Error details from failed push hook not displayed to HTTP client
topic: http_proto

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue937>
____________________________________________________