Hi!
> Any idea why there are so many TCP_DENIED/403, are these really
> failures ?
99% of TCP_DENIED requests for action=edit has & in URL (broken
clients)
> B
> For action=submit the difference between preview and save is in the
> result
> codes right ?
> I understood earlier that TCP_MIS
2009/10/12 Robert Rohde :
>> B
>> For action=submit the difference between preview and save is in the result
>> codes right ?
>> I understood earlier that TCP_MISS/302 is a successful save, right ?
>
Upon a successful save, action=submit uses a 302 to redirect to the
page view of the newly updated/
On Sun, Oct 11, 2009 at 6:03 PM, Aryeh Gregor
wrote:
> On Sun, Oct 11, 2009 at 3:28 PM, Erik Zachte
> wrote:
>> A
>> Any idea why there are so many TCP_DENIED/403, are these really failures ?
>
> Certain types of requests are blocked at the Squid level for various
> reasons. For instance, try w
On Sun, Oct 11, 2009 at 3:28 PM, Erik Zachte wrote:
> A
> Any idea why there are so many TCP_DENIED/403, are these really failures ?
Certain types of requests are blocked at the Squid level for various
reasons. For instance, try wgetting Wikipedia; you'll get a 403
because the default UA headers
On Sun, Oct 11, 2009 at 12:28 PM, Erik Zachte wrote:
> A
> Any idea why there are so many TCP_DENIED/403, are these really failures ?
TCP_DENIED is usually used for requests that the Squid is configured
to reject at the ACL level without even attempting to contact upstream
servers.
I'm not sur
The idea is to select edit and submit calls that are relevant to the
usability project and track edit/save ratio of filtered calls over time.
Bots will be filtered, "action=edit&redlink=1,.." will be discarded (as 95%
inadvertent edit calls), and some more.
I would appreciate help in decoding most
