Re: Redefine 401 error page

Le 27/05/2020 à 19:55, Willy Tarreau a écrit : Hi Christopher, On Wed, May 27, 2020 at 07:03:58PM +0200, Christopher Faulet wrote: Here are patches to handle customizable 401/407 messages. In fact, only the second patch is really meaningful. There is no change for the http-request auth rule

Re: Redefine 401 error page

Hi Christopher, On Wed, May 27, 2020 at 07:03:58PM +0200, Christopher Faulet wrote: > Here are patches to handle customizable 401/407 messages. In fact, only the > second patch is really meaningful. There is no change for the http-request > auth rule from the configuration point of view.

Re: Redefine 401 error page

Le 26/05/2020 à 10:22, Christopher Faulet a écrit : In HAProxy 2.2, I guess 401/407 responses may be generated using an http-request return rule, making http-request auth rule more or less deprecated. The only mess is to handle 2 different responses depending on the request path when the

Re: Redefine 401 error page

Le 26/05/2020 à 08:56, Willy Tarreau a écrit : Hi Joao, On Thu, May 21, 2020 at 09:41:19PM -0300, Joao Morais wrote: Hello list, the 401 is one of the http status code haproxy generates itself: https://github.com/haproxy/haproxy/blob/v2.1.0/doc/configuration.txt#L363 This cannot

Re: Redefine 401 error page

Hi Joao, On Thu, May 21, 2020 at 09:41:19PM -0300, Joao Morais wrote: > > Hello list, the 401 is one of the http status code haproxy generates itself: > > https://github.com/haproxy/haproxy/blob/v2.1.0/doc/configuration.txt#L363 > > This cannot however be overwritten using the errorfile

Redefine 401 error page

Hello list, the 401 is one of the http status code haproxy generates itself: https://github.com/haproxy/haproxy/blob/v2.1.0/doc/configuration.txt#L363 This cannot however be overwritten using the errorfile keyword as stated in the doc: