On 19/02/2020 20:17, Michael Osipov wrote:
> Am 2020-02-18 um 23:43 schrieb Mark Thomas:
>> On 18/02/2020 19:47, Michael Osipov wrote:
>>> If you say this is also a limitation in the Servlet API, it is worth to
>>> raise that as a clarification point?
>>
>> Sure. It won't happen until at least S
Am 2020-02-18 um 23:43 schrieb Mark Thomas:
On 18/02/2020 19:47, Michael Osipov wrote:
Am 2020-02-18 um 20:28 schrieb Mark Thomas:
Got it - I think. Let me re-phrase to see if I understand correctly.
You have a code fragment that issues a redirect.
The app submits a request with an header
On 18/02/2020 19:47, Michael Osipov wrote:
> Am 2020-02-18 um 20:28 schrieb Mark Thomas:
>> Got it - I think. Let me re-phrase to see if I understand correctly.
>>
>> You have a code fragment that issues a redirect.
>>
>> The app submits a request with an header "Expect: 100-continue"
>>
>> With
Am 2020-02-18 um 20:28 schrieb Mark Thomas:
On 18/02/2020 18:13, Michael Osipov wrote:
Am 2020-02-18 um 10:00 schrieb Mark Thomas:
On 17/02/2020 20:17, Michael Osipov wrote:
I have continued some tests on 8.5.51 with PUT requests and Expect: 100
continue header from HttpClient 5.0.
I have not
On 18/02/2020 18:13, Michael Osipov wrote:
> Am 2020-02-18 um 10:00 schrieb Mark Thomas:
>> On 17/02/2020 20:17, Michael Osipov wrote:
>>> I have continued some tests on 8.5.51 with PUT requests and Expect: 100
>>> continue header from HttpClient 5.0.
>>>
>>> I have noticed that the very same code
Am 2020-02-18 um 10:00 schrieb Mark Thomas:
On 17/02/2020 20:17, Michael Osipov wrote:
I have continued some tests on 8.5.51 with PUT requests and Expect: 100
continue header from HttpClient 5.0.
I have noticed that the very same code code fragment
What code fragment?
My bad, here it is:
F
On 17/02/2020 20:17, Michael Osipov wrote:
> I have continued some tests on 8.5.51 with PUT requests and Expect: 100
> continue header from HttpClient 5.0.
>
> I have noticed that the very same code code fragment
What code fragment?
> kicks in in the
> expect header evaluation when run as valve
I have continued some tests on 8.5.51 with PUT requests and Expect: 100
continue header from HttpClient 5.0.
I have noticed that the very same code code fragment kicks in in the
expect header evaluation when run as valve, but completely ignored when
run in a filter. Tomcat will simply signal t