git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: More detailed error message for 403 forbidden.

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 28, 2013, 19:11 UTC
Message-ID
<7vk3ortk3o.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130328183601.GA11914@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 13 quoted lines
> One problem is that the content body sent along with the error is not
> necessarily appropriate for showing to the user (e.g., if it is HTML, it
> is probably not a good idea to show it on the terminal). So I think we
> would want to only show it when the server has indicated via the
> content-type that the message is meant to be shown to the user. I'm
> thinking the server would generate something like:
>
>    HTTP/1.1 403 Forbidden
>    Content-type: application/x-git-error-message
>
>    User 'me' does not have enough permission to access the repository.
>
> which would produce the example you showed above.

Actually, isn't the human-readable part of the server response meant for this kind of thing? I.e.

	HTTP/1.1 403 User 'me' not allowed to accept the repository.
Previous: Yi, EungJunNext: Jeff King
Message 6 of 7 in “More detailed error message for 403 forbidden.”
  1. Yi, EungJunMar 27, 2013
  2. Jeff KingMar 28, 2013
  3. Jonathan NiederMar 28, 2013
  4. Jeff KingMar 28, 2013
  5. Yi, EungJunMar 31, 2013
  6. Junio C HamanoMar 28, 2013
  7. Jeff KingMar 28, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.