https://bz.apache.org/bugzilla/show_bug.cgi?id=60362
--- Comment #37 from Neil Brown <neil.brown.apa...@gmail.com> --- Hi, I've read through the discussion of this issue to date, in both the original bug report and this enhancement request. The Reason Phrase may be optional in the HTTP spec, but it's nonetheless useful to human beings. Given it's part of the HTTP/1.1 spec, I feel Tomcat users should be able to decide whether its usefulness is or isn't more important than the efficiency of not returning it. More importantly, removing the Reason Phrase, whether it is optional or not, represents a breaking change. Obviously it's up to the Tomcat team to decide whether the benefits of a breaking change outweighs its costs - the additional hit their users will take on upgrading. As an example, we have many APIs, running on older versions of Tomcat, with a large external user base. Whilst we have a suite of functional tests for these APIs (which include checking the Reason Phrase in the HTTP response status line) that can be easily fixed, we have no way of knowing whether existing customer's integrations currently rely on matching the Reason Phrase. Like many other users, we therefore couldn't risk upgrading to Tomcat 8.5+ without first going through an additional testing phase with these customers. Depending on the outcome, we would then need to take a view on whether it's acceptable to ask our customers to make changes to their API clients. I'd therefore like to add my vote for reinstating support for Reason Phrase, making it a configurable option if necessary. Thanks. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
