On Thu, Mar 28, 2019, at 7:14 PM, Alex Rousskov wrote:
> On 3/28/19 5:36 PM, Alex Rousskov wrote:
> > On 3/28/19 8:13 AM, cred...@eml.cc wrote:
> >> Is using the http_reply_access deny a viable option if all else fails
> >> to correct the issue until we can upgrade?
>
> > Probably it is not: I
On 3/28/19 5:36 PM, Alex Rousskov wrote:
> On 3/28/19 8:13 AM, cred...@eml.cc wrote:
>> Is using the http_reply_access deny a viable option if all else fails
>> to correct the issue until we can upgrade?
> Probably it is not: I am not sure, but based on my quick reading of the
> code and a basic
On 3/28/19 8:13 AM, cred...@eml.cc wrote:
> Is using the http_reply_access deny a viable option if all else fails
> to correct the issue until we can upgrade?
Probably it is not: I am not sure, but based on my quick reading of the
code and a basic test, http_reply_access does not support the
On Wed, Mar 27, 2019, at 4:23 PM, Alex Rousskov wrote:
> On 3/27/19 3:17 PM, sq...@buglecreek.com wrote:
> > Operating in reverse proxy mode. I'm trying to send a TCP reset in
> > response to the acl below:
> >
> > acl example_url url_regex -i [^:]+://[^0-9]*.example.com.*
> > deny_info
On 3/27/19 3:17 PM, sq...@buglecreek.com wrote:
> Operating in reverse proxy mode. I'm trying to send a TCP reset in response
> to the acl below:
>
> acl example_url url_regex -i [^:]+://[^0-9]*.example.com.*
> deny_info TCP_RESET example_url
> http_access deny example_url
>
> Looking at the
Operating in reverse proxy mode. I'm trying to send a TCP reset in response
to the acl below:
acl example_url url_regex -i [^:]+://[^0-9]*.example.com.*
deny_info TCP_RESET example_url
http_access deny example_url
Looking at the packets I see the following response:
HTTP/1.0 403 Forbidden
