DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39514>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=39514 ------- Additional Comments From [EMAIL PROTECTED] 2006-05-11 04:19 ------- The reply thank you. I also think that the modification of byterange is appropriate and Range should be processed on CGI side. And I know properly implimented http client is no problem. Simply, I hoped announcing clearly the fact that byterange processing which is applied to also CGI so far stopped being applied, as incompatibility between Apache-2.0.54 and 2.0.55. (I cannot grasp this change from CHANGES_2.0.55) Because perhaps the user of CGI and mod_jk/Tomcat which depend on the Range processing of Apache is... For example, MySQL say cleary "Incompatible change" in its change history <http://dev.mysql.com/doc/refman/5.0/en/news-5-0-19.html>. This is very helpful for mysql users. I think many Apache user are happy if Apache team announce distinguishing the difference with incompatible change and just bug fix. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
