>
>
>
>
>> E.g. "Transfer-Encoding: chunked" and "Content-Length" are mutually
>> exclusive, cannot be used at the same time, cannot be used more than
>> once. They should not be blindly copied.
>>
>
> Good question on that, I can take a look. I remove Content-Length from
> the downstream
>
>
>
> Status 500 means that some error happened during processing.
>
> Is there anything in the logs? Exceptions?
>
>
The 500 was generated by a downstream Tomcat 8.5.11 server, this one is
just trying to proxy the message.
> Maybe the browser closes the connection by its own decision,
>
>
> I'm working directly with the servlet api. Whats odd is it worked fine in
> 8.0.39. The response is set first:
>
>
>
Also, I just verified the issue doesn't occur using undertow 1.3.25
2017-03-12 15:32 GMT+03:00 Marc Boorshtein :
> Mark & Olaf,
>
> I'm working directly with the servlet api. Whats odd is it worked fine in
> 8.0.39. The response is set first:
>
>
Mark & Olaf,
I'm working directly with the servlet api. Whats odd is it worked fine in
8.0.39. The response is set first:
https://github.com/TremoloSecurity/OpenUnison/blob/1.0.9/unison/unison-server-core/src/main/java/com/tremolosecurity/proxy/filter/PostProcess.java
- lines 110-121
Then I
On 12 March 2017 05:12:09 GMT+00:00, Marc Boorshtein
wrote:
>I'm running tomcat 8.0.41 on a CentOS7 Docker container. Something
>very
>strange is happening. If I use a GET and return a 200 with JSON
>content
>the data gets back to my browser. But if I run a POST and
Am 12.03.2017 um 06:12 schrieb Marc Boorshtein:
> What am I missing?
>
IMHO:
* A code sample, and if that doesn't uniquely answer the next question:
* Are you working directly on the Servlet API or involve any other
library? (which version?)
Without this, it's hard to give some suggestion with
I'm running tomcat 8.0.41 on a CentOS7 Docker container. Something very
strange is happening. If I use a GET and return a 200 with JSON content
the data gets back to my browser. But if I run a POST and return a 500
with the content being JSON written to response.getOutputStream()
(including a