[
https://issues.apache.org/jira/browse/SCB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505906#comment-16505906
]
ASF GitHub Bot commented on SCB-653:
------------------------------------
liubao68 commented on a change in pull request #759: [SCB-653]Transfer-Encoding
and Content-Length can not be set to response
URL:
https://github.com/apache/incubator-servicecomb-java-chassis/pull/759#discussion_r194020198
##########
File path:
demo/demo-jaxrs/jaxrs-server/src/main/java/org/apache/servicecomb/demo/jaxrs/server/RequestClientTimeOut.java
##########
@@ -35,7 +35,7 @@
@Path("/add")
@POST
public int add(@FormParam("a") int a, @FormParam("b") int b) throws
InterruptedException {
- Thread.sleep(1000);
+ Thread.sleep(3000);
Review comment:
more than 2 seconds. I found time based test cases may not work property if
we using time smaller than 1 seconds. So used 1 second as a unit. Integration
tests takes more several seconds and I think is acceptable.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> When provider returns Transfer-Encoding header and Edge will cause problem
> --------------------------------------------------------------------------
>
> Key: SCB-653
> URL: https://issues.apache.org/jira/browse/SCB-653
> Project: Apache ServiceComb
> Issue Type: Bug
> Reporter: liubao
> Assignee: liubao
> Priority: Major
>
> When provider return Transfer-Encoding, Edge will copy this header to it's
> response, and edge will add Content-Length based on it's on strategy.
> Content-Length & Transfer-Encoding: trunked is conflict features of HTTP.
>
> We need to ignore HTTP internal headers of client response when sending it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
