New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HttpObjectEncoder#isContentAlwaysEmpty cannot be overridden by subclasses #6761
Comments
@vietj so you say it is package private and it should be not package-private ? Whats your use-case ? |
my use case is to not send content in a response to HEAD, Vert.x has a special subclass (that you actually created) of Another motivation is that we might want to handle the HEAD check with a custom implementation of |
any news about this ? |
Can you just create a PR for this change ?
On 26. May 2017 at 10:26:16, Julien Viet (notifications@github.com) wrote:
isContentAlwaysEmpty
|
sure I will |
…sses Motivation: Allow subclasses of HttpObjectEncoder other than HttpServerCodec to override the isContentAlwaysEmpty method Modification: Change the method visibility from package private to protected Result: Fixes netty#6761
Fixed by #6788 |
…sses Motivation: Allow subclasses of HttpObjectEncoder other than HttpServerCodec to override the isContentAlwaysEmpty method Modification: Change the method visibility from package private to protected Result: Fixes netty#6761
…sses Motivation: Allow subclasses of HttpObjectEncoder other than HttpServerCodec to override the isContentAlwaysEmpty method Modification: Change the method visibility from package private to protected Result: Fixes netty#6761
Expected behavior
the
HttpObjectEncoder#isContentAlwaysEmpty()
method is package private, so subclasses can change its behavior. Currently Vert.x has a subclass extendingHttpObjectEncoder
.Actual behavior
the
HttpObjectEncoder#isContentAlwaysEmpty()
method is package privateSteps to reproduce
n/a
Minimal yet complete reproducer code (or URL to code)
n/a
Netty version
4.1.8.Final
JVM version (e.g.
java -version
)n/a
OS version (e.g.
uname -a
)n/a
The text was updated successfully, but these errors were encountered: