You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the same request, its header may vary according to the underlying platform in terms of case sensitivity. Header has nothing to do with case sensitivity and it doesn't matter at the level of HTTP 1.1 speicification. But, in Java, header is represented as String and it does matter.
// Assumes the same request sent to Servlet and NettyassertEquals(httpByServlet.headerNames(), httpByNetty.headerNames());
At least, the above assertion should pass. To do that, Every header in returned a set of header string should be lower cased.
The text was updated successfully, but these errors were encountered:
Otherwise, it would be better to introduce HttpHeaders as a a representation for headers like http.requestHeaders() and http.responseHeaders() instead of http.headerNames, http.header, http.headers and http.setHeader.
Otherwise, HttpHeaders would be created for one exchange - accessors for request headers e.g. headers.get and mutators for response headers e.g. headers.set.
For the same request, its header may vary according to the underlying platform in terms of case sensitivity. Header has nothing to do with case sensitivity and it doesn't matter at the level of HTTP 1.1 speicification. But, in Java, header is represented as String and it does matter.
At least, the above assertion should pass. To do that, Every header in returned a set of header string should be lower cased.
The text was updated successfully, but these errors were encountered: