On 14/05/2019 21:57, Christopher Schultz wrote:
> Mark,
>
> On 5/14/19 15:47, Mark Thomas wrote:
>> On 14/05/2019 20:38, Igal @ Lucee.org wrote:
>>> On 5/14/2019 12:15 PM, Christopher Schultz wrote:
>
>>
>
> Then, Tomcat observes that the servlet or filter wants to put
> the response
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 5/14/19 15:47, Mark Thomas wrote:
> On 14/05/2019 20:38, Igal @ Lucee.org wrote:
>> On 5/14/2019 12:15 PM, Christopher Schultz wrote:
>
>
>
Then, Tomcat observes that the servlet or filter wants to put
the response into the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Igal,
On 5/14/19 15:38, Igal @ Lucee.org wrote:
> Chris,
>
> On 5/14/2019 12:15 PM, Christopher Schultz wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> All,
>>
>> bump
>>
>> It's hard to see anything with all the commit messages
On 14/05/2019 20:38, Igal @ Lucee.org wrote:
> On 5/14/2019 12:15 PM, Christopher Schultz wrote:
>>> Then, Tomcat observes that the servlet or filter wants to put the
>>> response into the penalty box and, instead of flushing the
>>> response and (possibly) closing the connection, it just
Chris,
On 5/14/2019 12:15 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
bump
It's hard to see anything with all the commit messages :)
On 5/9/19 12:52, Christopher Schultz wrote:
All,
What are the options we might have to "punish" an HTTP client that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
bump
It's hard to see anything with all the commit messages :)
On 5/9/19 12:52, Christopher Schultz wrote:
> All,
>
> What are the options we might have to "punish" an HTTP client that
> we don't like for some reason?
>
> Specifically, I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
What are the options we might have to "punish" an HTTP client that we
don't like for some reason?
Specifically, I'd like to be able to write a servlet that ties-up the
response to the client for a while for some bad behavior. For example,
