[GitHub] [tomcat] zhanhb commented on issue #175: Apply the suggestion in rfc7233

2019-07-01 Thread GitBox
zhanhb commented on issue #175: Apply the suggestion in rfc7233
URL: https://github.com/apache/tomcat/pull/175#issuecomment-507436005
 
 
   Good job, there is no issue with the range request now.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



[GitHub] [tomcat] zhanhb commented on issue #175: Apply the suggestion in rfc7233

2019-07-01 Thread GitBox
zhanhb commented on issue #175: Apply the suggestion in rfc7233
URL: https://github.com/apache/tomcat/pull/175#issuecomment-507295587
 
 
   For a put request, usually it won't have a header 'Range', The header 
specified in rfc 2616 is 'Content-Range'.
   What will happen to a put request if header 'Range' is specified?
   Put the content in specified URI and then return partial content of the 
entity. We can see existed source in tomcat, either 201 or 204 is returned, 
both have no response body content.
   IMO, this change can also be applied too.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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


With regards,
Apache Git Services

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org