-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Issue #4434 Implement context default request/response encodings. #4455
Issue #4434 Implement context default request/response encodings. #4455
Conversation
Signed-off-by: Jan Bartel <janb@webtide.com>
jetty-server/src/main/java/org/eclipse/jetty/server/Response.java
Outdated
Show resolved
Hide resolved
jetty-server/src/test/java/org/eclipse/jetty/server/CharEncodingContextHandler.java
Show resolved
Hide resolved
jetty-server/src/test/java/org/eclipse/jetty/server/CharEncodingContextHandler.java
Outdated
Show resolved
Hide resolved
jetty-server/src/main/java/org/eclipse/jetty/server/handler/ContextHandler.java
Show resolved
Hide resolved
Signed-off-by: Jan Bartel <janb@webtide.com>
Signed-off-by: Jan Bartel <janb@webtide.com>
@janbartel besides the "default" discussion, the build failed? |
…4434-default-request-response-encodings Signed-off-by: Jan Bartel <janb@webtide.com>
@janbartel I still don't like "default" and I would like it to be removed. Other than that, do we need changes in |
I don't understand your problem with having "default" in front of the name of the default request and response character encodings? That is what they are - defaults for the context. The servlet spec api is inconsistent: sometimes it uses "default" in method names eg getDefaultSessionTrackingModes() and web.xml elements eg default-context-path, sometimes it doesn't. However, the javadoc always makes clear that these are defaults and can be overridden by other means. I don't see why if the spec is inconsistent in naming we should be too in our own impl methods. As to your question about webdefault.xml, I don't see why we would need to add to it? |
…4434-default-request-response-encodings
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
@janbartel it's not a problem, just I don't like it because it is only ever used in that one place for the encoding, all other places don't have "default" in it.
I was asking whether we must provide a default or not - apparently not. |
Implement the new servlet spec web.xml settings of request-character-encoding/response-character-encoding and equivalent ServletContext methods.
Closes #4434