Re: [squid-users] What are the options for deny_info in this scenario?
OK so a custom 407 is the right answer for this case. instead of "proxy rejected the request" page from firefox or any other browser. by a localhost I meant a localnet host..(which from the proxy point of view is a localhost). So for the same request response I would use another thing that deny_info. Is there a template or a file that I can relate about this 407 response page? Thanks, Eliezer On 02/23/2014 06:31 AM, Amos Jeffries wrote: Auth requires a 407 status. Redirect is a 30x status. With deny_info you can send a 407 status with custom template "page" to display OR, redirect to another URL (localhost?) using 30x. But not both in the same response message. NP: the new URL may do or require authentication itself, but that is not related to the deny_info action. Amos
Re: [squid-users] What are the options for deny_info in this scenario?
On 22/02/2014 11:23 a.m., Eliezer Croitoru wrote: > Hey, > > Using squid 3.3.11 added ncsa basic auth and and a corresponding > deny_info to the acl which I assumed will redirect any login fail into > the localhost deny page. > On firefox I am getting auth fine with it but not deny_info page. > > In a case it should be like that then fine. > The deny_info directive is towards the auth acl of the ncsa > program\basic_auth. > > If needed more info I'm here. > > Eliezer Auth requires a 407 status. Redirect is a 30x status. With deny_info you can send a 407 status with custom template "page" to display OR, redirect to another URL (localhost?) using 30x. But not both in the same response message. NP: the new URL may do or require authentication itself, but that is not related to the deny_info action. Amos
