[SPEC] Encouraging HTTP Proxies to support Gemini hosts self-blacklisting

Oliver Simmons oliversimmo at gmail.com
Sun Feb 21 19:31:16 GMT 2021


I'm abstaining from commenting on the rest, but for the status code:

On Sun, 21 Feb 2021 at 18:54, Mansfield <mansfield at ondollo.com> wrote:
> ... or... the HTTP Proxy could just 404? 400? 204 Success and no content? 301 Moved permanently with a gemini URI? 403 Forbidden (not a *user* authz issue... but a *proxy* authz issue...)? 410 Gone? 451 Legal? (As an aside: there is a part of me that loves discussions/debates around what the right HTTP status code is for a given situation... there's another part of me that dies every time...)

404, 204 and 410 I think are definitely the wrong codes.
A 3xx redirect would be bad as it may cause confusion for non-gemini
folks and browsers.
451 & 403 would ~kinda make sense.

I'm going to add to the list these two, which I think may somewhat fit
when someone is trying to access gemini-only content via HTTP:

406 Not Acceptable:
> The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

405 Method Not Allowed:
> A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.

I'm not expert on HTTP though :p so I'm likely to be wrong.

- Oliver Simmons (GoodClover)


More information about the Gemini mailing list